incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r977419 - in /websites/staging/incubator/trunk/content: ./ guides/retirement.html report-next-month.html sitemap.html
Date Sun, 10 Jan 2016 16:04:30 GMT
Author: buildbot
Date: Sun Jan 10 16:04:30 2016
New Revision: 977419

Staging update by buildbot for incubator

    websites/staging/incubator/trunk/content/   (props changed)

Propchange: websites/staging/incubator/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Sun Jan 10 16:04:30 2016
@@ -1 +1 @@

Modified: websites/staging/incubator/trunk/content/guides/retirement.html
--- websites/staging/incubator/trunk/content/guides/retirement.html (original)
+++ websites/staging/incubator/trunk/content/guides/retirement.html Sun Jan 10 16:04:30 2016
@@ -130,40 +130,29 @@
 				the copyright requirements are fullfilled.  This is indicated
 				through the incubator status page.
+        <h2 id='decision'><img src="../images/redarrow.gif" />Deciding to retire</h2>
+<div class="section-content">
-				Before following the retirement steps, the remaining developers of the project should
be informed and vote
-				should happen on the projects dev list. After the vote, the IPMC must vote on the general
list to retire the
-				project. 
-			</p>
-				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).
+				In the vast majority of cases, a podling decides to retire on
+				its own and that decision is later formally ratified by the
+				Incubator PMC; very rarely, the IPMC may act on its own.
+				(This is deliberate mimicry of Board oversight of TLPs -- 
+				the language and role titles change but in general the Board
+				and the IMPC merely implement the wishes of the community.)
-				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:
+				Before the IPMC gets involved, a public discussion and
+				community vote SHOULD be held on the podling's dev list.  This
+				ensures that all podling stakeholders are properly informed and
+				have the opportunity to participate in the decision.
-				<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>
-				<li>If the project has not had a release for more than a year this fact will get
flagged by the Incubator report and the PPMC will be expected to get notified (either by one
of the mentors or an IPMC member). The initial discussion with the community is expected to
uncover and start addressing the underlying issues preventing the project from producing releases.
At this point the project is expected to be put on a monthly reporting schedule and the next
month's report is expected to articulate the steps and expected time frame to get to the release.
In case of a clear lack of progress for straight three months the [VOTE] thread on potential
retirement is expected to be started in IPMC.</li> 
-			</ol>
-				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)
+				The final decision to retire the podling takes the form of a
+				vote by the IPMC on general@incubator.
-<h3 id='steps-to-retirement'>Steps to retirement</h3>
+        <h2 id='steps-to-retirement'><img src="../images/redarrow.gif" />Steps
to retirement</h2>
 <div class="section-content">
 					Do the following steps to retire a project.
@@ -204,7 +193,6 @@
 					The user accounts of the projects committers do not need to be removed.

Modified: websites/staging/incubator/trunk/content/report-next-month.html
--- websites/staging/incubator/trunk/content/report-next-month.html (original)
+++ websites/staging/incubator/trunk/content/report-next-month.html Sun Jan 10 16:04:30 2016
@@ -67,7 +67,7 @@
 <a href="">Apache Incubator</a> Podlings needing to
prepare report for February</h1>
 <div style="text-align:right;">
-<i>Generated on 2016-01-10T14:04:35Z</i>
+<i>Generated on 2016-01-10T16:04:15Z</i>

Modified: websites/staging/incubator/trunk/content/sitemap.html
--- websites/staging/incubator/trunk/content/sitemap.html (original)
+++ websites/staging/incubator/trunk/content/sitemap.html Sun Jan 10 16:04:30 2016
@@ -1504,11 +1504,12 @@ Site map of <a href="http://incubator.ap
 <a href="guides/retirement.html#introduction">What is Retirement?</a>
-<a href="guides/retirement.html#steps-to-retirement">Steps to retirement</a>
+<a href="guides/retirement.html#decision">Deciding to retire</a>
+<a href="guides/retirement.html#steps-to-retirement">Steps to retirement</a>

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

View raw message