I believe there's value in adding new committers directly to the PPMC during incubation. We did this in Giraph and it worked out great. There's not enough institutional experience in the IPMC during Incubation (that's what the Mentors are for), so adding them in immediately helps to grow that as quickly as possible. As with commiters, should they not participate they can be dropped during graduation.
On Fri, May 25, 2012 at 10:19 AM, Jay Kreps <jay.kr...@gmail.com> wrote: > I think the advice from Alan was to wait for a while to add new committers > to the PMC, so I guess obviously if we make people wait a year we can't > really increase the PMC diversity very rapidly... > > Thoughts from any Apache folks on this? I think we are not too religious > one way or the other but are just looking for the official "best practice". > > -Jay > > On Fri, May 25, 2012 at 9:04 AM, Jun Rao <jun...@gmail.com> wrote: > >> I support graduation. >> >> Is diversity in PPMC a requirement for graduation? Currently, Kafka has >> diversity in committers, but not in PPMC. >> >> Thanks, >> >> Jun >> >> On Wed, May 23, 2012 at 8:14 PM, Jay Kreps <jay.kr...@gmail.com> wrote: >> >> > Hey All, >> > >> > Our little project is going pretty well: we have good discussion and >> > questions on the mailing lists, very active development, and a good set >> of >> > production usage. What do people think about pursuing graduation to be a >> > top-level project? >> > >> > The criteria for this are documented here: >> > http://incubator.apache.org/guides/graduation.html >> > >> > By my reading the main requirements on an incubator for graduation are: >> > >> > - Successfully create an apache release. >> > - Develop a diverse community (described in more detail here: >> > http://incubator.apache.org/guides/graduation.html#community). It >> boils >> > down to being an open community that fosters discussion and is not >> > dependent on a single company for success. >> > - Fulfill various technical requirements: project naming, etc. >> > >> > I think we have met these requirements. >> > >> > We struggled a bit with licensing and packaging issues but we got those >> > issues resolved and did a release and this should be pretty easy going >> > forward. >> > >> > This started as a LinkedIn project, and there are a still a number of us >> at >> > LinkedIn, but the discussion, JIRAs, patches, etc seems to be much more >> > well dispersed over a broad community of users and contributors. >> > >> > It would be good to here from anyone following the list what they think. >> > Are there other things we should do either before (or in parallel to) >> > pursuing graduation? >> > >> > I would also appreciate help from anyone with Apache experience >> navigating >> > the process. >> > >> > Cheers, >> > >> > -Jay >> > >>
