On Wed, Feb 26, 2003 at 12:04:32PM +0100, Torsten Curdt wrote: > <snip/> > > >>How about making one modification to this proposal... > >> > >>Host the Cocoon sandbox at Sourceforge, instead of Apache. Call it > >>cocoon-contrib or something. > > > >Hmmm... > > Hm... don't like this. The scratchpad would be to distant from the > cocoon itself.
Yes, just like the Wiki docs are distant from the xdocs. Just like the Wiki, it could benefit from much wider participation. > >>Why? Because then anyone can participate. It tears down any perceived > >>barrier between cocoon-dev and cocoon-users. Best of all, when code > >>eventually is 'promoted', there is a strong possibility of gaining new > >>Cocoon developers. Think of it as housing "alpha committers" as well as > >>"alpha code". > > Hm... don't understand why other rules should apply for the scratchpad > than for the "core project"? The core project's central rule is: only established committers can play. Nothing wrong with applying that to the scratchpad, if all you want to do is incubate code. I'm thinking, why not discard that rule for the sandbox, and use it to incubate *committers* as well as code? > >>The root problem is that Cocoon has more code than code maintainers. The > >>long-term solution is not to juggle the code more effectively, but to > >>gain more committers. THAT is why I think a cocoon-contrib @ sourceforge > >>would be a win in the long run. > > I mean - everyone can start a sourceforge project and see if it works > out and later contribute/offer the code to the cocoon project. Yes. Imagine if someone on cocoon-users started an umbrella project on SF for useful Cocoon snippets. Wouldn't this also be a logical place for alpha Cocoon stuff? > >sandbox.cocoondev.org? > > I think the scratchpad/sandbox should remain in the apache cvs! :) Just throwing around ideas.. --Jeff > -1 > -- > Torsten >
