Proposal for Apache Jakarta Ruper, A Java Resource Repository Subproject

5 February 2003

(0) rationale

Advanced build systems like Maven and Centipede use a system to download project dependencies as needed, instead on relying them to be in CVS. This has evident benefits, including less bandwith and disk space usage, and better and easier project and repository management.

(0.1) criteria

Meritocracy: Design decisions have been made following the Krysalis Community project Guidelines, that are very similar to the usual Apache project guidelines.

Community: There is a growing community of developers that are using the code in everyday projects.

Alignment: Uses many Jakarta components, and is compatible with Maven repositories.

Scope:

(0.2) warning signs

Orphaned products: Ruper is alive and used in Centipede, which is used to build OS projects.

As for

Krysalis Ruper is developed and maintained by Apache developers, that wish to bring this effort inside Apache itself.

(1) scope of the subproject

The purpose of this subproject is to create and maintain an implementation of a repository for resources, dealing with versioning, dependencies, and usable by the widest possible range of build tools. Mirroring and alternative ways of distribution are to be strongly pursued.

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

(3) identify the ASF resources to be created

(3.1) mailing list(s)

(no user mailing list yet, we are starting at Jakarta)

(3.2) CVS repositories

(3.3) Bugzilla

(4) identify the initial set of committers

These would be the core developers initially "responsible" of the project, that are willing to actively help.

The CVS repository though should be open to all Jakarta committers, as with the Gump project

(5) identify apache sponsoring individual

(6) open issues for discussion

  

RuperProposal (last edited 2009-09-20 23:31:33 by localhost)