incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "GrandCentralProposal" by AlanCabrera
Date Wed, 22 Feb 2006 15:34:04 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by AlanCabrera:
http://wiki.apache.org/incubator/GrandCentralProposal

New page:
= PROJECT PROPOSAL =

Grand Central, a home for Java Specs.

This proposal outlines the creation of a Top Level Project (TLP) of the Apache Software Foundation
(ASF) that will house all Java Specs.  These are the spec APIs, e.g. JSR-170 and SCA, not
the implementation behind the spec APIs, e.g. JCR and Tuscany.  This proposal will refer to
the work to build the spec APIs as ''completion'' and the work to implement the code behind
the spec APIs as ''implementation''.

= RATIONALE =

People now come to the ASF for completed APIs and their implmentations.  There are cases where
multiple projects need to use the same API.  There are also cases where outside project wish
to use a completed ASF API.  In the former case, it is not unsual to find two instances of
a completed API.  This can cause confusing internally as synergies between projects grow and
as outside projects and developers are forced to go on an Easter egg hunt for the API.

This proposal claims that a TLP is the best home for all completed APIs.  It removes redundant
instances of completed APIs.  It removes project specific names on spec jars, e.g. geronimo-servlet_2.4_spec.
 It makes it easier for the wider community to find and use completed APIs.

= MODUS OPERANDI =

The devil is in the details.

== Project Setup ==

Grand Central will get its code from Apache projects.  Each donating project will be the governing
body for that spec.  That project's PMC will designate commiters for that spec.  All designated
commiters will have access to Grand Central's entire Subversion repository; it is assumed
that designated commiters can be trusted not to fiddle with specs that lie outside their jurisdiction.

Since the ASF uses a single Subversion repository it should be simple enough to move the APIs
while keeping their provenance.  The project and the pantheon of APIs will be built using
Maven 2.

== Project Management ==

The API specs will be managed using the sponsoring project's Jira.  Releases of the API spec
will be governed and performed by the sponsoring project.

== Project Additions ==

All new donated API code from outside sources will be incubated using the standard and accepted
practices of the ASF Incubator.

== Project Shutdowns ==

Sponsoring projects may fade away and be closed.  In this case, the orphaned spec will go
up for adoption.  If there are no adopting ASF projects, the orphaned spec will be under the
care of the Incubator PMC.

'''ONCE A SPEC API IS IN GRAND CENTRAL, IT IS NEVER REMOVED'''

= INITIAL SOURCE =

Initial source will be moved from contributing projects.

= RESOURCES TO BE CREATED =

 * SVN Repository
 * Mailing Lists
 * Official Build Systems

= AVOIDING THE WARNING SIGNS =

'''NOT APPLICABLE'''

= Initial COMMITTERS =

Initial commiters will be submitted by each project PMC.  For the sake of simplicity, it is
asked that at most 3 committers per spec be submitted; this is not a hard rule.
 
= PROPOSED APACHE SPONSOR =

Every project PMC that is contributing a spec to this project is a sponsor for that spec.
 The collection of contributing PMCs will be Grand Central's PMC.

= MENTORS =

''needs to be filled''

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message