> This list might better be titled "High Priority Projects" or some such.
I agree. And, of course, I would like to see it more accurately reflect what things are actually high priority... maybe a few specific projects with of course target deadlines.. like docs for the 3.2 OOo release etc. > For example, for the user guides I would like to have a list of which > chapters need what work (reviewing, editing, updating to latest version > of OOo, writing missing sections, whatever is relevant). The problem, of > course, is keeping a detailed list up to date. I know that problem :-) It soon becomes a toss-up which is more work.. fixing the docs, or maintaining the list. > We could encourage people to contribute on the wiki as the project's > preferred method, but given that most of the contributors to the user > guides so far prefer to work in .ODT files through the OOoAuthors > website, I think it would be very counterproductive to say *only* on the > wiki. Exactly. What other methods do we have in place... the OOoAuthors process comes to mind. I don't know the process used there well enough to put any guidelines on the Contributor's 101 page. I am assuming that the processes in place there are best suited to larger projects... ie more than one page docs, especially the guides. This brings up another question... how do we ensure that the Wiki edits get back to the larger "master" docs - if any are being maintained in the OOoAuthors process? C. -- Clayton Cornell ccorn...@openoffice.org OpenOffice.org Documentation Project co-lead StarOffice - Sun Microsystems, Inc. - Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org For additional commands, e-mail: dev-h...@documentation.openoffice.org
