fantasai wrote: > "Daniel J. Wilcomb" wrote: > >>Thanks for the clarification. I'd like to talk in-brief about how this >>could be used to further centralize the documentation effort, rather >>than targeting yet another third-party solution. Is is possible to set >>up a dummy project called "documentation" and give me access to it in an >>administrative role? I'd like to see what this hierarchy looks like, >>and see if it appears immediately conducive to the type of effort we're >>looking at along these lines. >> > > The URL hierarchy has been discussed at length with the following result: > http://fantasai.tripod.com/Mozilla/2002/reorg/uri-plan/desc.txt > > The organization of the site is visitor-oriented rather than project-oriented > until you get into the /dev hierarchy. > > Much of the discussion took place in September of last year in the thread > titled "www.mozilla.org URI structure"[1]. Explanations of most parts of > the proposed structure can be found there. > > > [1] first post: > Markham, Gervase. "www.mozilla.org URI structure", > netscape.public.mozilla.documentation (2001-09-03). > message-id: [EMAIL PROTECTED] > http://groups.google.com/groups?selm=3B93FA9F.6030309%40mozilla.org >
What I'm trying to get a feel for is the volunteer effort that I'm trying to put some structure around. The idea being that there should be a central place for volunteers to go for documentation and writing contributions. That place should have a method of admins assigning volunteers work based on their abilities, the functionality for volunteers to mark that work "in-progress" on the "to-do" list, and a defined workflow for reviewing, editing, and finalizing the product of their efforts. I'm just curious as to how much of this functionality may be provided for within the architecture we're seeing at Zope. Not much of what this thing can probably do is visible to users at this time.
