I agree with the sentiment expressed -- OpenJPA has done a good job working together on a good code base with a growing, diverse group of contributors. I'm proud of the work that's been done here.
These days, the Board is wary of umbrella projects and is more comfortable with pushing smaller projects up to the top-level. Witness this with Shale, Cayenne, Tapestry, Velocity, and so on. I'd say TLP is the right place for OpenJPA based on my experience with the ASF, but this really is your (the contributing community's) decision. It goes without saying, but Craig would serve the community well and would be a great PMC Chair. Eddie On 4/30/07, Michael Dick <[EMAIL PROTECTED]> wrote:
+1. On 4/27/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote: > > > FWIW, I third the "vote". > > > On Apr 27, 2007, at 1:22 PM, Kevin Sutter wrote: > > > Patrick, > > > > On 4/27/07, Patrick Linskey <[EMAIL PROTECTED]> wrote: > >> > >> In terms of graduation, if we go the top-level route, I'd like to > >> propose Craig as the PMC chair. > > > > > > I second that "vote", if you are not interested. Craig has gotten > > us out of > > "Apache hot water" a few times with his background on Apache-isms. > > And, he > > has demonstrated his overall technical knowledge in JPA and > > persistence > > issues, in general. I would think Craig would make an excellent > > PMC chair. > > > > Kevin > > > > I think that he'd be a good fit since > >> he's quite active in the OpenJPA community, and also has a good > >> deal of > >> knowledge about and experience within Apache. I think that he > >> would do a > >> great job of continuing to represent Apache-isms to the OpenJPA > >> community and vice-versa. > >> > >> -Patrick > >> > >> -- > >> Patrick Linskey > >> BEA Systems, Inc. > >> _____________________________________________________________________ > >> __ > >> Notice: This email message, together with any attachments, may > >> contain > >> information of BEA Systems, Inc., its subsidiaries and > >> affiliated > >> entities, that may be confidential, proprietary, copyrighted > >> and/or > >> legally privileged, and is intended solely for the use of the > >> individual > >> or entity named in this message. If you are not the intended > >> recipient, > >> and have received this message in error, please immediately return > >> this > >> by email and then delete it. > >> > >> > -----Original Message----- > >> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >> > Sent: Monday, April 23, 2007 2:50 PM > >> > To: open-jpa-dev@incubator.apache.org > >> > Subject: [DISCUSS] OpenJPA Graduation > >> > > >> > OpenJPA has done a great job of forming a diverse community > >> > around a great code base whose IP has been reviewed and > >> > approved for release, and we're now a well-functioning, > >> > project in the incubator. So we are now at the stage when we > >> > should think about when and how to leave the incubator and > >> > graduate to the larger Apache community. The document at [1] > >> > describes readiness to graduate. > >> > > >> > There are two courses for graduating projects: to become an > >> > independent Apache TLP or to join an existing TLP as a > >> > sub-project. I believe that OpenJPA should become its own TLP > >> > for a few reasons: the community is already very diverse and > >> > has established a good working style; and there is no > >> > existing TLP upon which OpenJPA depends. There is some > >> > synergy with the DB project but no dependency relationship. > >> > > >> > As a TLP, OpenJPA would operate independent from other TLPs > >> > and be responsible to the Apache board. As a TLP, the OpenJPA > >> > community would decide on offering committerships to the > >> > project, and what and when to release, subject to the > >> > regulations of the ASF. > >> > > >> > So what does everyone think? > >> > > >> > Craig > >> > > >> > [1] http://incubator.apache.org/incubation/ > >> > Process_Description.html#Graduation > >> > > >> > Craig Russell > >> > Architect, Sun Java Enterprise System http://java.sun.com/ > >> products/jdo > >> > 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! > >> > > >> > > >> > >> Notice: This email message, together with any attachments, may > >> contain > >> information of BEA Systems, Inc., its subsidiaries and > >> affiliated > >> entities, that may be confidential, proprietary, copyrighted > >> and/or > >> legally privileged, and is intended solely for the use of the > >> individual or > >> entity named in this message. If you are not the intended > >> recipient, and > >> have received this message in error, please immediately return > >> this by email > >> and then delete it. > >> > >
