It makes sense. And it also seems to be a decent compilation of the points agreed in the earlier and lengthy discussion on the topic.
Cos On Sun, Aug 10, 2014 at 05:22PM, Roman Shaposhnik wrote: > Seems like attachments are eaten away by general@ > Including the patch bellow > > Index: content/guides/retirement.xml > =================================================================== > --- content/guides/retirement.xml (revision 1617182) > +++ content/guides/retirement.xml (working copy) > @@ -64,6 +64,7 @@ > <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> > <p> > Note, this is exactly what happens with board oversight of TLPs, > Index: content/incubation/Process_Description.xml > =================================================================== > --- content/incubation/Process_Description.xml (revision 1617182) > +++ content/incubation/Process_Description.xml (working copy) > @@ -34,7 +34,7 @@ > <li><a href="#Establishment">Establishment</a></li> > <li><a href="#Acceptance">Acceptance</a></li> > <li><a href="#Review">Review</a></li> > - <li><a href="#Termination">Termination</a></li> > + <li><a href="#TerminationRetirement">Termination > or Retirement</a></li> > <li><a href="#Continuation">Continuation</a></li> > <li><a href="#Graduation">Graduation</a></li> > </ul> > @@ -206,9 +206,12 @@ > their consideration. > </p> > </section> > - <section id="Termination"> > - <title>Termination</title> > - <p>If you receive a recommendation for termination then you have a > + <section id="TerminationRetirement"> > + <title>Termination or Retirement</title> > + <p>There are two ways for a project to cease incubation: Termination > +or Retirement. > + > +If you receive a recommendation for termination then you have a > problem. Chances are that there are either legal or structural > problems with your project that in the opinion of the Incubator PMC > are not resolvable within a reasonable time frame. A termination > @@ -217,6 +220,23 @@ > Directors and/or your Sponsor. You should be aware that several > Members of the Board are also Members of the Incubator PMC and as > such, an appeal is unlikely to be successful. > + > +Retirement is typically an internal decisions by PPMC. A retired project > +is a project which has been closed down by the PPMC or by the IPMC for > +various reasons. It is not longer developed at the Apache Incubator and > +does not have any other duties. > + > +Retirement can also be suggested by IPMC on the grounds of lack > +of releases for more than a year. However, since unlike termination, > +retirement is a voluntary process, the suggestion will have to be > +discussed and voted upon. > + > +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 ASF repository, when the copyright requirements are > fullfilled. > +This is indicated through the incubator status page. For more details on > +Retirement please see our <strong><a > href="../guides/retirement.html">Guide to Retirement</a></strong> > </p> > </section> > <section id="Continuation"> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
