incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1467163 - /incubator/public/trunk/content/guides/retirement.xml
Date Fri, 12 Apr 2013 04:12:26 GMT
Author: adc
Date: Fri Apr 12 04:12:26 2013
New Revision: 1467163

Updated retirement guidelines


Modified: incubator/public/trunk/content/guides/retirement.xml
--- incubator/public/trunk/content/guides/retirement.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/retirement.xml [utf-8] Fri Apr 12 04:12:26 2013
@@ -34,8 +34,12 @@
 				It is not longer developed at the Apache Incubator and does not have any other duties.
-				The source code of a retired project is available in SVN, when the copyright requirements
are fullfilled. 
-				This is indicated through the incubator status page.
+				It's important to view this process as being the retirement of
+				the podling community, not the code. It should not be implied
+				that the code is not for use - just that it has no community.
+				The source code of a retired project is available in SVN, when
+				the copyright requirements are fullfilled.  This is indicated
+				through the incubator status page.
 				Before following the retirement steps, the remaining developers of the project should
be informed and vote
@@ -43,8 +47,31 @@
-				In some cases the developers of a project might be opposed to retirement, while the IPMC
is in favour because
-				its members cannot see a succesfull graduation now or in future. In this case the IPMC
decides about the retirement. 
+				With that said, the ASF is not governed by votes, it is 
+				governed by consensus. It's important to note that in votes 
+				people often pile on without doing the appropriate background 
+				work (a +/-1 is easier than discussing the various options to 
+				reach consensus).
+			</p>
+			<p>
+				Votes in the ASF are usually used to confirm consensus that has 
+				already been achieved through discussion. So, in addition to 
+				supporting the suggestion to have a [DISCUSS] thread before a 
+				[VOTE] thread the following the following are guidelines with 
+				respect to podling retirement:
+			</p>
+			<ol>
+				<li>If the PPMC unanimously recommends retirement, it gets retired. No need for
a VOTE, just notify the IPMC, leave for 72 hours minimum and retire it.</li>
+				<li>If the mentors say it should be retired but the PPMC does not unanimously agree
then the podling should seek to recruit new mentors. No need to VOTE, just get on with it.</li>
+				<li>If there insufficient mentors willing to continue working with the project
then the IPMC has a problem to address on a case by case basis. The shepherd role ensures
that these cases are spotted during the reporting process. If necessary a [DISCUSS] thread
can be started and a sensible plan is developed (which may include a VOTE to retire, at this
point there should be no -1's as a -1 needs to be backed by a willingness to act and thus
this should have been surfaced in case 2) above.</li>
+			</ol>
+			<p>
+				Note, this is exactly what happens with board oversight of TLPs, 
+				the language and role titles change but in general the board 
+				merely implement the wishes of the community. The only time the 
+				board makes an actual decision is when the community is breaking 
+				down for some reason. This is done on a case by case basis after 
+				spending time trying to understand the situation (case 3) above)
 			<section id='steps-to-retirement'>
 				<title>Steps to retirement</title>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message