On 12/16/06, Earnie Boyd <mylists@progw.org> wrote:

Quoting "Frando (Franz Heinzmann)" <frando@xcite-online.de>:

>
> > The bad stuff is people using it as a place to store modules and
> > themes, this has always been a bad idea as you loose out the option of
> > using issues tracker, versions, and they are rarely included in
> > searches for any new wide spread security vulnerabilities.
>
> Of course you should publish working code as a module or a theme. But
> what about pre-alpha, not-yet-working code, experimental stuff, mere
> ideas that you want to share?

The use of CVS branches comes to mind. A cvs branch is created to
place code for development of new features for already released
modules. You then merge the HEAD and release changes using cvs
functionality to do so and then commit your changes as appropriate and
then clean up the branch.

I think one of the great things that Drupal has done is raised the bar for the use of version control by PHP developers. It's one of the things that has set us a bit apart. CVS branches are another level of complexity...something we need to spread even more to improve the quality of our code and ingrain best practices.

HOWEVER....think of sandboxes as a "safe" place where you can experiment? Probably not something we can do indefinitely....

Maybe, either through the Drupal Association or through a friendly neighbourhood Drupal company, we can offer a CVS space for anyone...

There are some existing free CVS spaces, too -- here's one that I found: https://freepository.com/services.html

Maybe part of the handbook write up on sandbox (anyone have a link? ideally it should mirror in part what contributions/README.txt says) can gather some of these free resources. I opened a documentation issue for this: http://drupal.org/node/103700