Maybe the discussion around moz.zope.org is important - it probably is - but that leaves the topic of this thread unaddressed: Which of the myriad technologies available to us is the best with regard to managing the volunteer documentation process? Let's try to keep this focused.
Explanation: The original purpose of this thread was to discuss possible technology solutions around organizing the Mozilla documentation effort. Specifically, the following: 1. I am trying to put structure around how volunteers get hooked up with documentation "work to be done" and how they go about performing that work and then sending it through a review process. 2. After discussions with Keyser Sosez, it has been determined that his efforts around organizing existing documentation and my effort to organize volunteers and "to-do" tasks should be coordinated, such that the outputs of my effort act as the ongoing inputs to his. 3. The question of whether there is a technological solution that naturally lends itself to managing a documentation project with relative stability and manageability of structure is the issue at hand. To recap: Maybe the discussion around moz.zope.org is important - it probably is - but that leaves the topic of this thread unaddressed: Which of the myriad technologies available to us is the best with regard to managing the volunteer documentation process? Let's try to keep this focused. ~Daniel. >> Chris Hoess wrote: > In article <[EMAIL PROTECTED]>, Gervase Markham wrote: > >>I would much rather you all saved your energies to help with >>moz.zope.org, which is the future of Mozilla's website. And yes, I know >>I haven't yet got around to saying how people can help; I'm extremely >>busy. I will do my level best to do that this weekend. >> > > > With all due respect, moz.zope.org has been the future of Mozilla's > website for about a year now (IIRC) with little noticable progress. Any > idea when the community at large will actually be able to hack on it? >
