[development] Seems I need to take sandbox in my own hands
gordon at heydon.com.au
Sat Dec 16 23:47:39 UTC 2006
I know that you want the sandbox accounts to say the way they are, and
you are willing to pay to get this.
Do not pay for this, I am willing to set up a cvs hosting with my host
company, and provide this service to anyone that wants it.
I have Gb of space that can be allocated, and TB of bandwidth that can
be donated to this. I can hand out most likely more that enough user
I think this is a bad change/enforcement of the policy for sandboxes,
and that the current system is a very valuable resource. I know that the
sandboxes are no longer really used for their original purpose, but
their use to a great help to development and share early code.
1 idea I did have is to move the sandbox to a 3rd repository, and we
will not have the chaos of the sandboxes in the contrib repos.
Karoly Negyesi wrote:
> ----- Start Original Message -----
> Sent: Sat, 16 Dec 2006 15:44:46 +0100
> From: Gerhard Killesreiter <gerhard at killesreiter.de>
> To: development at drupal.org
> Subject: Re: [development] Seems I need to take sandbox in my own hands
>> Karoly Negyesi wrote:
>>> If this sandbox rule is not changed really soon then I will simply open
>> The rules haven't changed, they are only enforced. The only
>> inconvenience to users is that they'll need to tell us to re-enable
>> their access in case they were using the sandbox for core development.
>> These are only very few people, unfortunatly.
>> Stop acting silly.
> I can not take an oath that every code I commit to my sandbox is intended for core. Some of the examples I mentioned -- JonBob's node access modules, our memcached session work -- definitely was and will not be for core.
> Further research shows that http://www.csoft.net/budget-vhost.html has unlimited CVS/SVN sub accounts for 15 bucks per month. This is even better. I will open the account on Monday or Tuesday.
More information about the development