On April 29, 2002, Nicola Ken Barozzi wrote:
>> 2. Author reads "How-To Write <document-type />". > > Contributing -> documentation Yes, there will be a link from the contributing section, but I thought I'd demonstrate how to write a "how-to" by actually writing a few how-tos. > >> 3. Author consults topic status list (a web page on cocoon web site) to >> make sure no other draft on this topic is in process. > > Or search on the aggregated titles page. Yes, but I want to minimize duplication of effort. But aggregated titles alone may not show that a draft effort in process -- or would you add its status? >> - If this review is handled off-list, could we set up a generic email >> alias (like [EMAIL PROTECTED])? Emails could be forwarded to one >> or >> several committers, including myself, as well as stored? Don't we want >> to ensure this process is not overly dependent on the responsiveness of >> a single committer? > > I'd keep the process loose. > Just propose, get /quick/ feedback, and write it. > -1 for the mailing list. We did it for XSPs, and it was a complete > failure. But don't you think documentation has a much broader scope/concern than XSP? I take encouragement in the fact these efforts exist formally (and appear to be working successfully) in other open source projects: Linux, Zope, Apache, etc. > Besides, we don't get that many offers for documentation ;-) I think that fact reflects the maturity of an open source project. Besides, Cocoon attracts content management people like myself. My instincts tell me our existing users have a lot of skills and experience they could bring to the effort. > >> 5. If topic approved, author drafts outline and sends to editor for >> review. > > To you? Ok :-) Yes, of course, but the point is to build a process that is sustainable without the efforts of a single person. Granted, sustainability and momentum won't happen overnight, but it should be the goal. >> <snip what="proposed steps 10-16" /> > > IMHO too much red tape. Maybe for an advanced writer, but what if an author actually wants this feedback? Remember, I'm talking about users, not developers. >> Thanks for *any* input. > > Maybe more concise still? ;-) I'll keep trying, with your help ;) Diana --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
