...
Process | The JA-SIG Incubation Process is 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. |
...
- 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 ][SB: I think this is a good criteria for review in the case where there has been conflict. I don't think it's a requirement.]
- 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
- Use of Integration with other JA-SIG projects [ JS: use seems to strong. and, given point below unneccary ]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
...
- The project will be promoted into a fully sponsored JA-SIG project
- The project will remain in Incubation [SB: Is there a limit to the time in incubation?]
- The project will be asked to hibernate after a period of little activity (it may move out of hibernation at a later date)
- 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.
Notes
A sandbox or "contrib." environment may also be made available to projects before entering a Candidate phase. This is a less formal status than Candidate. Projects in contrib. may be put there to share with the community and garner support and participation. Contrib projects may be nominated to enter incubation, at which point the formal incubator acceptance criteria would be applied. Projects may also be nominated to enter incubation from outside contrib, or during project formation. In other words, a presence in contrib is not a pre-requisite to becoming an incubation candidate, not is progress towards incubation necessary for contributions into the contrib area.