Hi all, As Axion has always been one of the candidates for apache db I do not see why they should go through an incubator process? We know the aims of the project. We know the existing codebase. And we know the developer team. I see no need for any incubation.
>From my side as a member of the DB PMC a clear +1 to incorporate Axion directly as a DB subproject without any intermediary status. cheers, Thomas > -----Original Message----- > From: Rodney Waldhoff [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 16, 2003 2:53 PM > To: [email protected]; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: incubation requirements for axion at apache db? > > > Axion (<http://axion.tigris.org/>) is a Java-based relational database > engine that was among the set of "seed projects" named in the > proposal for > Apache DB (<http://db.apache.org/pmc/initial-proposal.txt>). > > The Axion team is considering moving to the Apache DB project, and > depending upon the source, there seem to be some conflicting > reports on > what exactly that will entail. > > The Apache DB bylaws (<http://db.apache.org/management.html>) and > subproject submission guidelines > (<http://db.apache.org/newproject.html>) > state that a subproject must be approved by a 3/4 majority > Apache DB PMC. > They make no mention of the Apache Incubator project, nor of > any specific > incubation process. > > (Similarly, by the way, for the Jakarta project bylaws and subproject > submission guidelines.) > > Pages on the Incubator site (e.g., > <http://incubator.apache.org/process.html>), seem to place > the incubator > in a central role in the sub-project adoption process, although the > precise process to be followed is apparently neither "complete [n]or > completely authoritative". > > The Axion team would like to understand precisely what the incubation > requirements and process, if any, is necessary for a move to > the Apache DB > project. > > A draft proposal for Axion at Apache DB follows. It includes some > additional background material. > > - Rod <http://radio.weblogs.com/0122027/> > > -------------- > Proposal for Creating an Axion sub-project within the Apache > DB Project > > (0) Rationale and Consideration of Sub-Project Criteria > > Axion is a relational database engine currently developed and released > under an Apache/BSD-like license. > > While it has not yet had a formal 1.0 release, Axion is not a > new project. > Axion has had three binary "milestone" releases, the first of > which was > released over a year ago (9 July 2002) [1]. The project has > been under > active development since early 2002 [2] and has shown regular > and diverse > growth in both the development and user communities. > > The Axion team has operated under meritocratic guidelines [3] > similar to > and derived from those of the ASF since its inception. > > The Axion project has strong personal ties to the Apache > community. Many, > indeed most members of the Axion community are contributors > or committers > to one or more ASF projects, serve on one or more ASF PMCs or are ASF > members. [4] > > The Axion project has strong technical ties to the Apache community. > Axion uses several ASF libraries [5], and as a project, has > contributed > code back to those libraries where appropriate [6]. Some existing ASF > projects use or support Axion currently, others have > expressed an interest > in doing so (notably the Apache Directory Project). > > Similarly, many current ASF projects could advantage of a robust, > ASF-licensed Java database engine and there several projects > with which > Axion could collaborate on infrastructural components. > > (1) Scope > > The project will create and maintain a (primarily relational) database > engine and related utilities, to be distributed under an ASF-license. > > (2) Initial Source > > The initial source of the project will be the material > currently available > from <http://axion.tigris.org/>. This source is currently > available under > an ASF-style license, and the community has elected to > migrate to an ASF > license. > > (3) Apache DB Resources to be Created > > (3.1) Mailing Lists > > * [EMAIL PROTECTED] > * [EMAIL PROTECTED] > > (perhaps others as needed) > > (3.2) Version Control Repository > > * cvs/db-axion on cvs.apache.org > > (3.3) Web Site > > * http://db.apache.org/axion/ > > (3.4) Other > > Issue tracking (bugzilla), email archive (eyebrowse), etc. entries as > appropriate. > > (4) Initial Set of Committers > > The initial set of committers will the same as that of the > Axion project > at Tigris at the time of the move. See > <http://axion.tigris.org/servlets/ProjectMemberList>. > > (A) End Notes > > [1] <http://axion.tigris.org/releases/index.html> > [2] <http://axion.tigris.org/servlets/SummarizeList?listName=cvs> > [3] <http://axion.tigris.org/guidelines.html> > [4] Compare those with the "Developer" role or stronger at > <http://axion.tigris.org/servlets/ProjectMemberList>, or the list at > <http://axion.tigris.org/unbranded-source/browse/*checkout*/ax ion/LICENSE.txt?rev=HEAD> with <http://www.apache.org/~jim/committers.html> [5] Currently Axion uses 8 external libraries when you include required and optional build, test and run-time dependencies. Of these, 6 are ASF libraries (Ant, Jakarta-Commons-Codec, Jakarta-Commons-Collections, Jakarta-Commons-Logging, Jakarta-Regexp, Maven). [6] Most notably, the org.apache.commons.collections.primitives.* package, which was initially developed within Axion then contributed to Jakarta-Commons, although there have been other less substantial enhancements and contributions. ---------------
