On Wed, Nov 21, 2012 at 4:26 AM, Benson Margulies <bimargul...@gmail.com> wrote: > So, permit me to ask another, related, question. It seems to me that > the IPMC is concerned with the fact that a project is ready to leave, > but not so much which where it is going. A proposal to form a new TLP > is, I think, a straightforward question to the board, and the IPMC's > action is to make a recommendation to the board. > > A proposal to be integrated into an existing project is, I think, > within the authority of the existing product's PMC. If Project A > wishes to invite the members of Podling B to join and integrate their > code, then this looks to me like it could just happen without any > approval in advance from the board or even the IPMC. Voting in > committers is a PMC task, voting in PMC members is a PMC task with > board lazy approval, and copying (ip-cleared) code from one place in > ASF source control to another is a PMC task. > > I think that IPMC graduation votes in this case are a nice thing, but > it seems by this logic that they are not necessary. > > Does this make sense?
I think you raise a very important question. In a sense, the way I see it there has to be a joint recommendation to the board in such a case with IPMC vouching for all the mechanics of the proposed community (knowing the Apache Way, being capable of releases, being capable of due diligence, etc.) and a top level PMC vouching that they do, indeed, see a fit. That said, I'm not quite sure how to best draft such a joint proposal. Thanks, Roman. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
