...
Inspired by Apache, via GlobusA
Nomenclature
- The JA-SIG Incubation Process is wholistically the activities and mechanism whereby open source software projects are proposed, incubated, evaluated, progressed, and emerged from incubation
- The JA-SIG Incubation Working Group (JIWG) are the people who oversee this process
- The JA-SIG Board leads JA-SIG, overseeing and supporting the Working Group and the process they execute
- Projects are the software subject to incubated, progressing from Candidate Project status through in-incubation Incubated Project status and ideally emerging as a fully-fledged Sponsored Project.
The JA-SIG Incubation Working Group
The JA-SIG Incubation Working Group will oversee the process through which new projects move from a Candidate Project to an accepted Incubated Project, through review, to a fully sponsored project. The JIWG is responsible for
- assisting proposed projects in conforming to JA-SIG guidelines [ JS: I'd like to see "providing guidance" cut down to "assisting projects in conforming to JA-SIG guidelines" – this also implies we need definitive, published guidelines.]assisting
- assigning a Project Mentor, a member of the community assigned to helping help the Incubator Incubated Project reach acceptance
- evaluating progress of the Incubator Incubated Project on a regular (quarterly?) basis and recommending escalation to a sponsored project, continued support, or retirement---based on a set of established criteria , according to established criteria
Process
This process describes how a candidate project would progress from submission to full acceptance as a JA-SIG Project.
...
- A proposed name for the project;
- The short preface for the mailing lists, if this project is accepted (*-dev, *-user, etc);
- A proposed Project Lead, with contact information;
- A A list of the proposed committers for the project;
- An An overview of the aims of the project;
- A A technology overview;
- An An overview of any current user base or user community, if applicable;
- An An overview of how the project relates to other parts of JA-SIG;
- A A summary of why the project would enhance and benefit JA-SIG and higher education;
- A A pointer to any current information (for example, an existing Web page) for the project
...
2. Review of Submissions
The JIP JIWG (and possibly the JA-SIG Board)
- Discuss the project
- Vote on its acceptability
- Accept the project, which official officially becomes a project in incubation within the auspices of JA-SIG
- Nominate a Mentor for the project, typically a JA-SIG community stakeholder who will act as a bridge between the JIP JIWG and the project (mentor becomes a member of the JIPJIWG)
- Assist the Incubator Incubated Project in the initial start-up steps for using the JA-SIG SVN, Confluence and Jira (for roadmap and bug tracking), licensing, and mailing lists
...
The minimum requirements that a project must meet prior to being successfully promoted to a fully supported product of JA-SIG 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 AG: Do we want to wait this long before we have them provide this? For example, don't we want to be up front with them on the JA-SIG license policies? Should this be part of earlier "Candidate discussions")
- Check of project name for trademark issues.
* JS: trademark registration for project name help by JA-SIG
...