...
Process | The JA-SIG Incubation Process is wholistically holistically the activities and mechanism whereby open source software projects are proposed, incubated, evaluated, progressed, and become full-fledged JA-SIG sponsored projects |
|---|---|
Incubation WG | The Incubation Working Group (Incubation WG) are the people who oversee this process |
Mentor | The Mentor is a particular person assigned by the Incubation Working Group to shepherd a candidate project through incubation |
Board | The JA-SIG Board leads JA-SIG, overseeing and supporting the Working Group and the process they execute |
Projects | Software to incubated, progressing from Candidate Project status through in-incubation Incubated Project status and ideally emerging as a fully-fledged Sponsored Project. |
...
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:
Legal
- 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.
* JS: JA-SIG will assist in trademark registration for project name help by JA-SIG.
Community
- 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.
- JA-SIG voting practices have been adopted and are standard practice
- The project can articulate instances of having weathered and resolved conflict. 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. [ JS: this seems too hard to quantify to be particularly useful ]
- 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 [ JS: also unsure about this – how do we define engagement? It certainly seems reasonable to have basically independent projects ] . 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
- Use of other JA-SIG projects [ JS: use seems to strong. and, given point below unneccary ]
- Develop synergistic relationship with other JA-SIG projects
...