Page Comparison

Inspired by Apache, via Globus

...

Preincubation and contrib projects may indicate that hosting is provided by JA-SIG, but no other endorsement is implied.

The minimum requirements that a project must meet to exit the state of preincubation are:

• Project goals are clearly defined.
• Design documents are public and reasonably stable.
• Extensive coding on the project core is underway. Proof of concept or skeletal implementations are not sufficient.

The minimum requirements that a project must meet to exit the state of incubation (and should be working on fulfilling as part of the incubation process) are:

...

These requirements are dependent on approval of a JA-SIG licensing policy. 

• All code properly licensed.
• No non-licensed or license-incompatible dependencies in the code base;.
• Software license grant complete;.
• Contributor License Agreements on file (both individual and corporate agreement);.
• Copyright agreement in all source files.
• Check of project name for trademark issues.  JA-SIG will assist in trademark registration for project name.

...

• Demonstrate an active and diverse development community. Preferably the list of original committers will have grown beyond the original set (and institution) in the proposal, but this is not a requirement.
• Demonstrate that the project has a reasonable expectation for support in the future, for example, if any single contributor leaves the project continued support will exist;.
• The above implies that new committers are admitted according to JA-SIG practices;.

Governance

• A project steering committee has been created to oversee the project, or the project committers and an existing steering commitee agree that an existing steering committee will steer the project.  In the case of portlets a new steering committee is probably not required.  Initially the JA-SIG uPortal Steering Committee will oversee portlets as well.  Once the process grows to too large for that committee the intention is to appropriately group portlets for the process of governance. 
• JA-SIG voting practices have been adopted and are standard practice.
• The project has weathered and resolved conflicts where they have arisen. Good-natured and well-meaning disagreement of vision, requirements, and implementation are a reality of community source development. JA-SIG desires that incubated projects work through these "growing pains", as the software is developed and additional committers and adopters become involved, before emerging from incubation. Incubation provides an opportunity to face conflict with the assistance of an Incubation Mentor and the support of the Incubation Working Group. 
• Release plans are developed and executed in public by the committers.
• At least one release has occurred during the Incubation process.
• Engagement by the incubated community with the larger JA-SIG community.   The incubated project may engage on a technical level by integrating with an existing JA-SIG projects.  It is also desirable for the prospective project to have been presented / discussed at the JA-SIG Unconference or annual conference.

Alignment & Synergy

• Integration with other JA-SIG projects where appropriate.
• Develop synergistic relationship with other JA-SIG projects wherever possible.

Infrastructure

• SVN module has been created on JA-SIG server.
• Three required mailing lists have been used.
• Issue tracker is being used (JIRA).
• Roadmap for project is present in Confluence.
• Project website is current.
• All non-sensitive (i.e. passwords, etc) information in the above tools is publicly accessible.

4. Periodic Review

Projects in preincubation will undergo periodic reviews (at least quarterly) which may have one of five outcomes:

1. The project will be promoted into Incubation.
2. The project will remain in Preincubation. If the project's sponsor is no longer affiliated with JA-SIG, a new sponsor must be found or the association with JA-SIG is discontinued.
3. The project will be asked to hibernate after a period of little activity. (It may move out of hibernation at a later date.)
4. The project will be asked to retire due to lack of progress
5. The project discontinues its association with JA-SIG (by self-sponsoring or migrating elsewhere).

Projects in incubation will undergo periodic reviews (at least quarterly) which may have one of four outcomes:

1. The project will be promoted into a fully sponsored JA-SIG project.
2. The project will remain in Incubation Incubation.
3. The project will be asked to hibernate after a period of little activity. (it It may move out of hibernation at a later date.)
4. The project will be asked to retire due to lack of progress.

5. Promotion to full-fledged product

The project may be promoted to a fully sponsored JA-SIG project when it meets Legal, governance, community, alignment & synergy and Infrastructure requirements outlined above.  When requirements are met the IWG will recommend to the board that the project be promoted to sponsored status.  Final acceptance of sponsored project must be approved by the board.

6. Termination of Project Sponsorship

Either JA-SIG or the Project Steering Committee may terminate sponsorship according to the following rules:

• The IWG may vote to recommend sponsorship termination to the JA-SIG Board, which in turn may vote to terminate sponsorship.
• The Project Steering Committee may vote to terminate sponsorship.
• Once one of the above in voting procedures is completed, termination is effective at the second scheduled meeting of the Board or Committee that did not execute the vote, or in 90 days, whichever comes first. If the sponsorship termination vote is rescinded, termination is no longer effective.

It is expected that an effort will be made to resolve any issues related to the sponsorship termination prior to the procedures being put in effect.

Notes