On Jul 12, 2004, at 5:39 PM, Brian Behlendorf wrote:
On Mon, 12 Jul 2004, Stefano Mazzocchi wrote:Brian Behlendorf wrote:
On Mon, 12 Jul 2004, Rodent of Unusual Size wrote:In that case, we might decide to accept a new project into the incubator for the same purpose, but decide not to accept the sucky code.why? if the idea excites people but the code sucks, are we going to turn it down?
java.apache.org history shows a long history of failures in incubating projects without code. jakarta doesn't, exactly because we established that rule.
It would be a *major* step back if we lifted that requirement.
Keep in mind that availablility of the code is a requirement during incubation, of course. The question is what's an appropriate bar to set *before* a project is accepted into the incubator.
I can imagine cases where it might be reasonable to suggest such a thing ;)
geir
-- Geir Magnusson Jr 203-247-1713(m) [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]