On 14-07-2005 04:30, "Henri Yandell" <[EMAIL PROTECTED]> wrote:
> On 7/11/05, Henri Yandell <[EMAIL PROTECTED]> wrote:
> 
>> 2) How much of the Incubator process would apply to Commons?

All of it.

>> Many of
>> the exit conditions are automatically passed just by being a part of
>> Commons. [http://wiki.apache.org/incubator/ExitingIncubator]

So you go through real quickly. I once guided MerlinDeveloper (big external
package with one new developer) through incubation in a week. Just fill out
the template and all the bullets (yes the community is healthy, yes the ip
issues are resolved, yes the pmc wants to do this, yes yes all ok) and run
the proper votes, less work than figuring out whether it should happen as
part of the incubator, and you're making sure you have all your I's dotted
:-)

>> Please
>> don't take this question as an attempt to weasel out of having to
>> incubate.

Heh. Incubation is something *you* do. The incubator pmc restricts itself to
watching and nodding gently if possible.

> To provide another example in the area of this question.
> 
> Would we create a mailing list just for commons-csv, or would we
> create a commons-incubator mailing list to be used for each component
> that works its way through the incubator?

Since the developers you're bringing into jakarta commons are already apache
committers, and since further development discussion would occur on the
commons mailing list, I wouldn't bother with worrying about setting up a
PPMC or a new mailing list or anything like that. You're just going through
the "IP clearing" part of incubation, jakarta can do the community
aggregation within the existing jakarta commons infrastructure, you just
declare that its fine and we believe you :-).

Similarly with SVN, you could import into /incubator/..., then when the IP
stuff is fixed you svn mv everything into j-c. Done and done, with svn
history showing the correct IP clearing process.


Just my 2 cents,


Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to