[Docutils-develop] reorganize the sandbox?

[David G. <go...@us...>]

There sandbox is becoming an interesting place.  There are several
useful applications of Docutils (ZReST, PythonPoint writer,
DocFactory), the LaTeX writer has been picked up by a second
developer, and the PySource writer is up for grabs.  It seems to me
that these projects have outgrown the developer-oriented sandbox.

With the possibility of two or more people working on the same sandbox
project, perhaps it's time to re-think the sandbox organization.
Sandbox projects are inside directories with peoples' name on them.
This may give people pause, thinking that the projects are "owned" and
off-limits, when in fact they should be open and inviting.  A
half-finished project is a sad thing, and we should encourage
participation from anyone who's interested.

I think projects ought to be emphasized, rather than people.  Perhaps
we should create a new top-level "projects" directory, open to
participation.  A README.txt file at the top of each project could
identify the project coordinator and outline any requirements (like
"please run patches by me before checking them in").  Some of the
material in the sandbox is not project-oriented though, and should
remain in the sandbox.

When we move a directory, the continuity of the CVS history of the
files will be broken unless we ask the SourceForge staff to move the
directories for us.  They appear to be willing to do this (they've
done individual files for me in the past), but I'd rather ask all at
once than in dribs and drabs, so we'll need an organized plan.

Opinions?  Is this necessary or useful?  Should we move existing
projects or just new ones?  Would anyone like to volunteer for their
project to move over?  Does anyone object to this approach?

-- 
David Goodger  <go...@us...>  Open-source projects:
  - Python Docutils: http://docutils.sourceforge.net/
    (includes reStructuredText: http://docutils.sf.net/rst.html)
  - The Go Tools Project: http://gotools.sourceforge.net/