<div>Hopefully we can have something really useful built to support the patch creation/submissions process...</div>
<div> </div>
<div>A web-based UI (a bit like Launchpad), where you didn't need any installed software to create patches. The patches could then be added to a 'pending approval' section, where users could vote on how good/useful they think the patch is - therefore making it easy for people with commit access to see which patches are the best/most wanted.</div>
<div> </div>
<div>Also making it easy for people to see what needs adding to - perhaps having hidden tags within the XML files like in the wiki 'stub' or 'needs work' etc - these could then be filtered so somebody who knows a lot about a certain thing can search for the pages which need updating/working on, that are relevant to them.</div>
<div> </div>
<div>I'm thinking tag clouds, filtering pages and voting mechanisms.<br clear="all"><br>-- Alex<br><br><br></div>
<div class="gmail_quote">On Thu, Jan 22, 2009 at 2:35 PM, Jacob Santos <span dir="ltr"><<a href="mailto:wordpress@santosj.name">wordpress@santosj.name</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I had to laugh, because I have like 6 or 7 patches for WordPress which haven't been committed yet and I'm still waiting. I also don't think you are being sarcastic, which I mean you know, it actually isn't too easy to have patches committed.<br>
<br>Yeah, it is super easy to submit patches, we'll have to see how quick the commit process is. It really depends on who is babysitting the repository and how many people have commit access. If one or two people from Automattic or outside entity have commit access, then I'll tell you right now, that it won't be easy, based upon the patch process for the WordPress Tests Repository. If they don't think your documentation correction is worth it, then you'll have made the patch for nothing.<br>
<br>If you do think that the patch is worth it, then you are going to have to battle to the death and debate those with commit access to death on the correction or addition. I really don't see a lot of people contributing to it, besides Automattic and a few other people. Really it depends on how they implement the patch system.<br>
<br>Translations will be easier and I think many in the translation team will contribute to those portions.<br><br>Jacob Santos<br><br><br>Lorelle VanFossen wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="Wj3C7c">@tai - translations are the hope and could be much easier with this new technique.<br><br>Imagine how easy it would be to submit patches to improve translation!<br><br>Lorelle<br></div></div>------------------------------------------------------------------------
<div class="Ih2E3d"><br><br>_______________________________________________<br>wp-docs mailing list<br><a href="mailto:wp-docs@lists.automattic.com" target="_blank">wp-docs@lists.automattic.com</a><br><a href="http://lists.automattic.com/mailman/listinfo/wp-docs" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>
<br></div></blockquote>
<div>
<div></div>
<div class="Wj3C7c"><br>_______________________________________________<br>wp-docs mailing list<br><a href="mailto:wp-docs@lists.automattic.com" target="_blank">wp-docs@lists.automattic.com</a><br><a href="http://lists.automattic.com/mailman/listinfo/wp-docs" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-docs</a><br>
</div></div></blockquote></div><br>