Grant Ingersoll wrote:

However, if the receiving PMC doesn't want to do incubation b/c it feels there will be enough a community in a decent amount of time, then why does it matter? Isn't it the receiving PMC's responsibility? Why should Labs care what happens to a project that has left labs for another place within the ASF? I fail to see how the situation is any different from the case where Thorsten had gone directly to a PMC and said "I'd like to start a subproject named Droids" and that PMC either votes for it or not.

I think the trick becomes that we don't want there to be two projects that are Droids (even if there named differently), one in Labs and one in the receiving PMC, even though this seems perfectly legal under the ASF license. Thus, I don't see why the Labs project can't just be marked as "completed" and then refers to the new subproject.

+1, this has been my point for a while, now :)

Have the PMC (Incubator or other TLP) vote to accept the lab as it's very
own podling/subproject, and be done with it.

The only thing "impossible" here is for the lab to vote something to be
promoted to TLP, because I think the board would ask if the Labs had all
of the resources and energy invested in ensuring its success as a project.
(As opposed to investing in a successful code base, which labs can do
quite well.)


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

Reply via email to