Proposal for "The Commons" - A Jakarta Subproject version 1.0 - 5 Mar 2001

(0) rationale 

Apache-Java and Jakarta originally hosted product-based subprojects, consisting of one major deliverable. The Java language however is package-based, and most of these products have many useful utilities. Some products are beginning to break these out so that they can be used independently. A Jakarta subproject to solely create and maintain independent packages is proposed to accelerate and guide this process.

(1) scope of the subproject

The subproject shall create and maintain packages written in the Java language, intended for use in server-related development, and designed to be used independently of any larger product or framework. Each package will be managed in the same manner as a larger Jakarta product. To further this goal, the subproject shall also host a workplace for Jakarta committers and a master index of reusable packages related to Jakarta products.

(1.5) interaction with other subprojects

(1.5.1) the sandbox

The subproject will host a CVS repository available to all Jakarta committers as a workplace for new packages. Before release to the public, a sandbox package must be accepted to the library, or sponsored by another Jakarta subproject. 

(1.5.2) the directory

The subproject will also catalog packages and other resources available to the public related to other Jakarta subprojects and ASF projects. This will be a dynamic catalog, like Bugzilla and Jyve, similar in functionality to download.com, cpan.org, or SourceForge.net. New entries may be added by Jakarta committers, developers, and users. Entries by developers and users will be approved by a committer before being made public.  

(2) identify the initial source from which the subproject is to be populated

The initial packages would be based on existing ASF codebases, including those that provide services for DataSource/Database Pools, XML Configuration, Message Resources and i18n, JNDI and Naming, and Testing Suites. The initial committers have agreed to first create and maintain a Database Connection Pool package, along with related testing suites and subproject infrastructure.

(3) identify the Jakarta resources to be created 

(3.1) mailing list(s)

jakarta-commons-general jakarta-commons-DBCP (database connection pool) jakarta-commons-sandbox (unreleased packages)

(3.2) CVS repositories

jakarta-commons jakarta-commons-sandbox

(3.3) Bugzilla 

program - commons components - Web site, Directory, DBCP

(3.4) Jyve FAQ (when available)

commons-general commons-DBCP commons-sandbox

(4) identify the initial set of committers

Morgan Delagrange Ted Husted Geir Magnusson Jr. Costin Manolache  Remy Maucherat Craig R. McClanahan Ignacio J. Ortega Rodney Waldhoff David Weinrich

Proposed Guidelines and a FAQ are also available at

< http://husted.com/about/commons/ >

###