incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <nicolas.lale...@hibnet.org>
Subject Re: Shepherd for EasyAnt
Date Wed, 04 Jul 2012 10:04:48 GMT

Le 4 juil. 2012 à 03:44, Dave Fisher a écrit :

> 
> On Jul 3, 2012, at 12:06 PM, Nicolas Lalevée wrote:
> 
>> 
>> Le 3 juil. 2012 à 19:00, Jukka Zitting a écrit :
>> 
>>> Hi,
>>> 
>>> On Tue, Jul 3, 2012 at 6:44 PM, Nicolas Lalevée
>>> <nicolas.lalevee@hibnet.org> wrote:
>>>> The primary target for Easyant will be being a subproject of Ant.
>>> 
>>> Is there something that the Incubator can do for EasyAnt that the Ant
>>> PMC can't? If not, I don't see a need to wait for this to happen.
>> 
>> I guess that the incubation process for EasyAnt was about training the people "attached"
to the project so they learn how to build a proper ASF community, release, and check IP clearance.
Since the Ant PMC doesn't contain enough active members so handle such project income, this
should happen with the help of the Incubator.
> 
> How has the refactoring due to an expected contributor's unwillingness to sign an ICLA
effected the project? This issue makes me think that the main purpose of going through the
incubator was to inoculate the project's IP, not that there is anything wrong with that. If
it is true that the IP is correct is there any reason for the Incubator not to transfer the
EasyAnt project to the Ant PMC? Does that make sense?

I guess that would work.
I always wondered how to make the EasyAnt committers be able to be part of a PMC. I was thinking
that they could become "trustworthy" while being in the incubator. But then it would be effectively
awkward to promote them into the Ant PMC without it to be involved. So this is indeed a job
for the Ant PMC.

> Note I used the term "transfer" to recognize a different situation or standard from "graduation
to a TLP".
> 
> Somehow the IPMC would need to certify the IP in the podling and then the target PMC
would have to accept the podling.
> 
> VOTEs:
> 
> (1) PPMC - if it can.

We kind of already did that with the mentors. See project status about IP clearance [1].

> (2) Target PMC - to confirm that it wants the podling's IP.

The Ant PMC already voted that by sponsoring it I guess. But I am not sure we were all aware
of the consequence: having a subproject with only one active PMC member (me), doing a release
will need some involvement until some of the EasyAnt committers become part of the PMC.
I'll ping the PMC to confirm you're still ok with that.

> (3) IPMC - to confirm IP and transfer.
> (4) Board - do the bylaws require a fourth vote?


Let me know what would be needed at the IMPC level so the transfer can happen.

Nicolas

[1] http://incubator.apache.org/projects/easyant.html


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message