-0 in moving sandbox to incubator
For me sandbox and incubator have 2 different purposes.
Incubator: Bring *external* code people into ASF, resolving license
issues and allowing new people to learn the ASF way of doing things.
Sandbox: New and experimental code from existing and *trusted*
o How to handle dormant sandbox projects?
subversion does cheap copies, so why not use them?
well ...not sure if it helps to hide them somewhere
under the bed. Then we could leave them where they
are.
o What is the definition of dormant?
perhaps: one that is no longer under
On Tue, 2005-07-12 at 07:32 +0200, Torsten Curdt wrote:
snip/
Thoughts?
snip
I think what we require is some process.
+1
IMHO this would be a good idea regardless
o How to handle dormant sandbox projects?
subversion does cheap copies, so why not use them?
the only downside to
[Spawned from thoughts on the Commons Csv component proposal]
How does the following sound:
* Move the Sandbox over into the Incubator project.
* SVN commit rights remain the way they are currently.
* Jakarta Commons and Apache Incubator come up with a simpler
checklist of exit conditions
snip/
Thoughts?
Hm... Your proposal does make sense
but I am not quite sure if incubator
is the right way to deal with the
sandbox. Reasons why:
o Sandbox components are usually
small. Whether they can exist
as their own full project is
questionable. Or do you want
to incubate