- how to manage the patch queue
Well, IMO what's most important here is, assuming this is open to everyone, not just people with doc-karma, to keep it moderated. So eg. all patches get sent to the appropriate mailinglist, and can be blocked/added there. It's imporant to do so, since most people don't bother reading about coding styles, about styles of writing (in first person, third person, etc.), and such. So, a bit of moderation there is important I think.
This is indeed an important aspect of the system and deserves (requires) a lot of thought. For now all it does is allow the user to save the file but eventually it will likely save the files to the server (patch queue) for translators to find/manage/commit. Since some patches will be perfect, some require light editing, some major editing, and some bogus, how to deal with all of that is a question too. As are guidelines for crediting patch creators in the commit message, and being sure we write a "the manual is granted all rights to this content, blah blah blah..." in the proper place.
And simplifying the HOWTO for patch creators is a good idea too, as I'm sure we can come up with a quick guide about writing style and format.
Regards, Philip
