incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "RetiringPodlingsProposed" by AlanCabrera
Date Sat, 22 Dec 2012 19:24:38 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "RetiringPodlingsProposed" page has been changed by AlanCabrera:

New page:
== Garnering Consensus ==

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.

Firstly, the ASF is not governed by votes, it is governed by consensus. Secondly, in votes
people often pile on without doing the appropriate background work (a +/-1 is easier than
discussing the various options to reach consensus).

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:

 1. 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.
 1. 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.
 1.  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.

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)

== Retirement Cleanup Steps ==

This presumes that the Incubator has made the decision to retire a podling (with the Incubator
PMC, podling and sponsoring part of the ASF all agreeing). The following needs to be done
(largely in this order):

 1. Inform -dev/-user mailing lists of the decision
 1. If JIRA: Move the JIRA project to a Retired category and Retired (read-only) permissions
 1. If Bugzilla: Close the project in Bugzilla so new issues cannot be created (ASFInfra JIRA)
 1. Make the wiki read-only (ASFInfra JIRA)
 1. Update the website to indicate that the podling is retired
 1. Move the podling to the Retired section of the Incubator site
 1. Update the Incubator status page
 1. Make the SVN read-only
  a. Remove entries from asf-authorizaton - this makes the directory rw to the Incubator PMC.
  a. Add entries to asf-mailer.conf and send mail to cvs at
 1. Ask that the mailing lists be shutdown (ASFInfra JIRA)
 1. Indicate the podling is closed down in the next board report and in incubator-info.txt
 1. If the podling is listed on the Incubator's ReportingSchedule, remove it from that listing.

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

View raw message