[development] CVS contribtions/sandbox changes

Frando (Franz Heinzmann) frando at xcite-online.de
Sat Dec 16 13:58:53 UTC 2006


Hmm,
it is still not clear to me why you would 'close' the sandbox.

Is it the 31 MB disk space that the sandbox needs?
Is it the fear of people storing copyrighted material there?
Or the fear of people being to lazy to actually release their code as a 
module or theme and instead leaving it in a sandbox?

I think the drupal sandbox is a great feature for the community that 
should be kept as it was. A place to play with drupal core and to share 
pre-alpha / experimental code, no matter wether it's core or contrib code.

 > 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? IMHO, this is what a sandbox is for. To 
store code that is not yet ready for being published. As soon as you 
open a project for it, people will expect that the code is working or at 
least being worked on. That might not be true for some pre-alpha or 
testing code, but this code can still be worthable enough for some 
people, probably only developers, to be published somewhere. And where 
to publish it if not in a sandbox?

So see this as a pledge of an very ordinary drupal community member for 
the survival of the sandbox as it used to be ;)

Maybe just publish a policy that clearly states that a) modules and 
themes should be published as modules and themes and not lie in a 
sandbox and b) that only code closely related to drupal is allowed to be 
stored in the sandbox.

regards,
frando

Kjartan Mannes schrieb:
> Greetings,
> 
> Originally the Sandbox was created as a place to put core patches that 
> were pending review, as we did not have any issue tracker back then. 
> Since then the project module has grown and can now cover most of the 
> original purpose of the sandboxes. Since then sandboxes have been used 
> for many original uses, some that are good and some that aren't so good. 
> The good stuff are what the sandboxes were originally intended for, 
> large or very experimental Core changes that weren't ready for a proper 
> issue. 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.
> 
> Since sandboxes still have some limited use we aren't completely getting 
> rid of it, but it will be cleaned up. To make this happen we have made 
> the current sandbox directory read-only, and only approved people can 
> commit new files and changes. All the current data in the sandboxes will 
> remain there until January 15, 2007. Sandboxes who have had people 
> request write access, and had this granted will remain and all the rest 
> will be archived and moved out of the repository. To request access file 
> an issue against the infrastructure tracker 
> (http://drupal.org/node/add/project_issue/drupal_org_maintenance) it 
> will then be handled. I'm pretty sure the CVS administrators will be 
> lenient with regards to what is considered core patches and experimental 
> stuff, but I doubt we will approve people using the sandboxes as a place 
> to host mp3 collections, non-Drupal projects or even whole websites.
> 
> Modules and themes that are in active use and/or development will be 
> moved to the proper location upon request, this will preserve the CVS 
> history whereas re-committing them to the right place will loose the 
> history. Please file an issue on the infrastructure tracker for this: 
> http://drupal.org/node/add/project_issue/drupal_org_maintenance.
> 
> I know some people will be unhappy with these changes, but having 
> thousands of files randomly stored in the CVS repos doesn't add value 
> most of the time. We definitely want to help provide the tools for cool 
> Drupal developments, but it will happen under slightly more orderly 
> rules than the current wild mess.
> 

PS some quick stastics:
3204 files in total
2709 files with
^.*\.(php|module|install|inc|mysql|sql|css|js|txt|po|pot|sql|gif|png|jpg|pdf|swf|htm|html)$

    0 files with ^.*\.(mp3|avi|mpeg|mpg|ogg)$

    3 files with size > 500 kbytes
   24 files with size > 100 kbyes
3099 files with size <  50 kbytes
2530 files with size <  10 kbytes


More information about the development mailing list