-The IPMC will also express a democractic opinion. For those seeking to graduate to a subproject +The IPMC will also express a democratic opinion. For those seeking to graduate to a subproject this vote is to approve the transfer. For those seeking to graduation as a top level project, this -will be a recommendation to the board. Expect IPMCers to ask questions about the project +will be a recommendation to the board. Expect IPMC-ers to ask questions about the project including about the choice of destination. This is part of the normal process.
@@ -228,7 +228,9 @@- TODO: content + Subprojects are accepted by a Project Management Committee. + The Incubator Project Management Committee needs to approve + the graduation of the podling to a subproject.
- Graduation is the first step in what is hopefully a long - road. There are some issues which incubation may not - cover. -
--When a project graduates, then the infrastructure resources (mailing lists, websites, source, etc.) -need to be transferred from the Incubator to a project's new home. -
-- Check list: -
-svn move
- the podling source tree
- .htaccess entry to redirect traffic from the old URLs to the new.
- /www/incubator.apache.org on
- people.apache.org.
- project.xml
- - Each project needs to be able to manage security. By - their nature, these issue need to be dealt with in - private. These issues may either be dealt with on a - separate list or by the private list. Which list is - suitable for security issues should be noted. -
-Projects need to cut releases. Apache projects need to understand how to -cut Apache releases. +cut Apache releases.
Podlings do not need to actual publish a release to demonstrate that @@ -379,6 +274,12 @@ incubator project management committee is usually the simplest way to do this.
++If you are going to cut a release (which is highly recommended), then please read +the Incubator Release Management Guide for hints, +tips and guidelines for cutting a release that will get approved by the IPMC without +problems. +
+One of the exit criteria is that the podling needs to have an open and diverse +meritocratic community. +To show this to the IPMC, it can be beneficial to vote and accept a couple of +new contributors during incubation: this shows that you are open to accept new +developers and grow your community (note: this is not a requirement, but will help +the graduation process). It will also allow you to diversify +your community (which is a requirement for graduation). +
++The openness of your community is not only measured by the number of accepted contributors. +You will need to have open and respectful discussions on the open mailinglist(s). You need to +show that you can resolve technical conflict without destroying personal relationships. If +you can manage this, then you have shown to be a lively, active and successful community. +
+@@ -431,8 +349,115 @@
TODO: content
TODO: content
+TODO: content. NOTE: is there any actual physical stuff happening with the hand over?
+ Graduation is the first step in what is hopefully a long + road. There are some issues which incubation may not + cover. +
++ When a project graduates, then the infrastructure resources (mailing lists, websites, source, etc.) + need to be transferred from the Incubator to a project's new home. +
++ Check list: +
+svn move
+ the podling source tree
+ .htaccess entry to redirect traffic from the old URLs to the new.
+ /www/incubator.apache.org on
+ people.apache.org.
+ project.xml
+ + Each project needs to be able to manage security. By + their nature, these issue need to be dealt with in + private. These issues may either be dealt with on a + separate list or by the private list. Which list is + suitable for security issues should be noted. +
+