...
- A proposed name for the project
- The short preface for the mailing lists, if this project is accepted (*-dev, *-user, etc). Incubating portlets will use the existing portlet mailing lists.
- A proposed Project Lead, with contact information
- A list of the proposed initial committers for the project
- An overview of the aims of the project
- A technology overview
- An overview of any current user base or user community
- An overview of how the project relates to other parts of JA-SIG
- A summary of why the project would enhance and benefit higher education
- A pointer to any current information (for example, an existing Web page) for the project
...
Once a project has been accepted for incubation, JA-SIG Incubation working group (IWG) would then:
- Accept the project, which officially becomes a candidate project in incubation under 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 IWG and the project (mentor would also then serve as a member of the IWG)
- Assist the candidate project in the initial start-up to use the JA-SIG resources like SVN, Wiki, Issue Tracker, and mailing lists. These resources should be set up in JA_SIG infrastructure unless IWG decides otherwise.
- SVN: It is expected that new portlet projects would begin in the sandbox area of the JA-SIG SVN and move to the portlets SVN when promoted to sponsored status. Other new projects would begin a new project under the JA-SIG SVN.
- JIRA: Each incubating project would get its own JIRA project.
- WIKI: Each incubating project would have its own WIKI space on the JA-SIG wiki server. Incubating portlets will use the exisitng portlet space.
- Lists: Incubating portlets will use the existing portlet mailing lists while each regular projects will have its own mailing list.
- Assist the candidate project in performing appropriate licensing, contribution, trademark, and other legal arrangements
...