yes, the project has the freedom to implement anything it wants, by both the letter and spirit. "related" is a wide-open door. geir On May 4, 2007, at 1:36 PM, Dain Sundstrom wrote: > I personally define OpenJPA by the persistence engine and not the > spec it implements. A good persistence engine is very hard to > write, but adapting it to new persistence specs if fairly easy in > comparison. I would like to see the scope be limited to java > persistence with an eye toward the current JPA space, but want the > project to have the freedom to implement JDO, CMP, SDO or any java > persistence spec that pops up. > > Said another way, if this project decides to implement JDO, should > it have to go into another TLP or a sub project? > > -dain > > On May 4, 2007, at 8:50 AM, Geir Magnusson Jr. wrote: > >> +1 >> >> Only comment is that we might consider narrowing the scope a tiny >> bit, saying something like >> >> ".... to be known as Apache OpenJPA, chartered with the >> implementation of the Java Persistence API as well as related >> object persistence technology, for dis..." >> >> Just so that the board doesn't feel that the scope is *too* >> broad. It says the same thing, but emphasizes what the project >> currently does. >> >> That said, it would probably be fine as is :) >> >> geir >> >> >> On May 3, 2007, at 3:22 PM, Craig L Russell wrote: >> >>> This vote is to send the attached draft board resolution to the >>> incubator for the purpose of graduation from the incubator to the >>> Apache OpenJPA project. >>> >>> +1 We're ready; let's graduate >>> >>> 0 Don't care >>> >>> -1 Let's wait >>> >>> Establish the Apache OpenJPA project >>> >>> WHEREAS, the Board of Directors deems it to be in the best >>> interests of the Foundation and consistent with the >>> Foundation's purpose to establish a Project, to be known as >>> Apache OpenJPA, related to the implementation of >>> object persistence, including, but not limited to, >>> Java Persistence API, for distribution at no charge to the >>> public; >>> >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management >>> Committee (PMC), be and hereby is established pursuant to >>> Bylaws >>> of the Foundation; and be it further >>> >>> RESOLVED, that the OpenJPA PMC be and hereby is charged with >>> the creation and maintenance of Apache OpenJPA; >>> and be it further >>> >>> RESOLVED, that the office of "Vice President, Apache >>> OpenJPA" be and >>> hereby is created, the person holding such office to serve at >>> the direction of the Board of Directors as the chair of the >>> OpenJPA PMC, and to have primary responsibility for >>> management of >>> the projects within the scope of responsibility of the >>> Apache OpenJPA >>> PMC; and be it further >>> >>> RESOLVED, that the persons listed immediately below be and >>> hereby are appointed to serve as the initial members of the >>> OpenJPA PMC: >>> >>> Eddie O'Neil >>> Geir Magnusson Jr. >>> Brian McCallister >>> Patrick Linskey >>> Craig Russell >>> Kevin Sutter >>> Abe White >>> Marc Prud'hommeaux >>> >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Craig Russell >>> be appointed to the office of Vice President, Apache >>> OpenJPA, to serve >>> in accordance with and subject to the direction of the >>> Board of >>> Directors and the Bylaws of the Foundation until death, >>> resignation, retirement, removal or disqualification, or >>> until >>> a successor is appointed; and be it further >>> >>> RESOLVED, that the initial OpenJPA PMC be and hereby is >>> tasked >>> with the migration and rationalization of the Apache >>> Incubator >>> OpenJPA podling; and be it further >>> >>> RESOLVED, that all responsibility pertaining to the Apache >>> Incubator OpenJPA podling and encumbered upon the Apache >>> Incubator >>> PMC are hereafter discharged. >>> >>> Craig Russell >>> DB PMC, OpenJPA PPMC >>> clr@apache.org http://db.apache.org/jdo >>> >>> >> >