cvs: peardoc /en/chapters rfcs-entities.xml /en/chapters/rfcs orphan-packages.xml orphan-proposals.xml

http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs-entities.xml?r1=1.7&r2=1.8&diff_format=u
Index: peardoc/en/chapters/rfcs-entities.xml
diff -u peardoc/en/chapters/rfcs-entities.xml:1.7 peardoc/en/chapters/rfcs-entities.xml:1.8
--- peardoc/en/chapters/rfcs-entities.xml:1.7	Mon May  4 17:42:24 2009
+++ peardoc/en/chapters/rfcs-entities.xml	Mon May  4 18:35:49 2009
@@ -1,6 +1,8 @@
 &chapters.rfcs.error-handling;
 &chapters.rfcs.estrict-compatibility;
 &chapters.rfcs.header-comments;
+&chapters.rfcs.orphan-packages;
+&chapters.rfcs.orphan-proposals;
 &chapters.rfcs.protected-members;
 &chapters.rfcs.qa-team;
 &chapters.rfcs.rules-on-rules;

http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/orphan-packages.xml?view=markup&rev=1.1
Index: peardoc/en/chapters/rfcs/orphan-packages.xml
+++ peardoc/en/chapters/rfcs/orphan-packages.xml
<?xml version="1.0" encoding="UTF-8"?>
<chapter version="5.0" xml:id="chapters.rfcs.orphan-packages"
         xmlns="http://docbook.org/ns/docbook"
         xmlns:xlink="http://www.w3.org/1999/xlink"
>
  <info>
    <title>Orphaned packages</title>

    <date>2005-02-18</date>
  </info>

  <para>
    This RFC has been ratified in PEPr as
    <link xlink:href="&url.pear.pepr.proposal;192">proposal #192</link>.
  </para>

  <section xml:id="chapters.rfcs.orphan-packages.problem">
    <title>The Problem</title>

    <para>Sometimes a package is left without care for a long time. It becomes
    lonely and full of bugs. This is a very sad situation and somebody needs
    to step up to remedy it.</para>
  </section>

  <section xml:id="chapters.rfcs.orphan-packages.whatis">
    <title>What can be considered an orphaned package?</title>

    <para>The following are considered orphaned packages:</para>

    <itemizedlist>
      <listitem>
        <para>A package with bugs open for longer than <emphasis>2
        months</emphasis> and the developers have not commented on the bug or
        made any commits to CVS during that time frame.</para>
      </listitem>

      <listitem>
        <para>A package that has no open bugs and has bug fixes committed to
        CVS but does not have a release within <emphasis>6 months</emphasis>
        of the bugs being fixed.</para>
      </listitem>

      <listitem>
        <para>A package owned by somebody who is commonly known to be
        inactive.</para>
      </listitem>

      <listitem>
        <para>A package denounced by its leads (i.e. The lead actually says
        that he is no longer maintaining it on pear-dev)</para>
      </listitem>
    </itemizedlist>
  </section>

  <section xml:id="chapters.rfcs.orphan-packages.contacting">
    <title>Contact process</title>

    <para>A QA core-team member tries to contact the current maintainers and
    developers (cc'ing the QA list) asking about an update about their work on
    the package.</para>

    <para>A package lead answers::</para>

    <itemizedlist>
      <listitem>
        <para>He states that he has no interest in the package anymore, he
        allows QA team to take the necessary steps</para>
      </listitem>

      <listitem>
        <para>He states that he still intends to work on the package, but is
        busy at that point. Either a timeframe will then be decided upon by
        the lead and QA during which some activity must occur (i.e. I'm going
        to be busy the rest of this month but I'll get back to it on the 3rd
        of next month) OR a second lead developer will be sought to continue
        development</para>
      </listitem>
    </itemizedlist>

    <para>If no answer reaches the list in <emphasis>two weeks</emphasis> QA
    will consider the package orphaned. If the lead doesn't have the time he
    should write a mail to the list stating he needs more time to sort things
    out.</para>
  </section>

  <section xml:id="chapters.rfcs.orphan-packages.findlead">
    <title>Finding a new lead</title>

    <para>A message will be sent to pear-dev asking for volunteers.</para>

    <section xml:id="chapters.rfcs.orphan-packages.findlead.stepup">
      <title>Somebody steps up</title>

      <para>If you are willing to take over a package you must notify the QA
      list and state who you are and why you want to take over.</para>

      <para>If the QA team feels the person who stepped up is appropriate and
      capable, the team will make this person a new maintainer. In case
      several persons step up a case by case study will be carried out to
      assign new maintainer-ship.</para>
    </section>

    <section xml:id="chapters.rfcs.orphan-packages.findlead.nobody">
      <title>Nobody wishes to take over</title>

      <para>A QA core team member will mark the package as orphaned.</para>
    </section>

    <section xml:id="chapters.rfcs.orphan-packages.findlead.status">
      <title>Orphan status</title>

      <para>If a package is orphaned, a warning and a call for maintainers
      will be displayed on the main package page.</para>
    </section>
  </section>

  <glossary xml:id="chapters.rfcs.orphan-packages.glossary">
    <info>
      <title>Glossary</title>
    </info>

    <glossentry>
      <glossterm>QA-Team</glossterm>

      <glossdef>
        <para>refers to the whole QA team (core and subscribed mailing list
        members)</para>
      </glossdef>
    </glossentry>

    <glossentry>
      <glossterm>QA core team</glossterm>

      <glossdef>
        <para>refers to the <link xlink:href="http://pear.php.net/qa/">7
        elected members</link> (only 6 presently) </para>
      </glossdef>
    </glossentry>
  </glossary>
</chapter>

http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/rfcs/orphan-proposals.xml?view=markup&rev=1.1
Index: peardoc/en/chapters/rfcs/orphan-proposals.xml
+++ peardoc/en/chapters/rfcs/orphan-proposals.xml
<?xml version="1.0" encoding="UTF-8"?>
<chapter version="5.0" xml:id="chapters.rfcs.orphan-proposals"
         xmlns="http://docbook.org/ns/docbook"
         xmlns:xlink="http://www.w3.org/1999/xlink"
>
  <info>
    <title>Orphan PEPr proposals</title>

    <date>2005-01-26</date>
  </info>

  <para>
    This RFC has been ratified in PEPr as
    <link xlink:href="&url.pear.pepr.proposal;188">proposal #188</link>.
  </para>

  <section xml:id="chapters.rfcs.orphan-proposals.problem">
    <title>The problem</title>

    <para>It happens more or less often, that</para>

    <orderedlist>
      <listitem>
        <para>PEPr proposals get stuck in a specific proposal phase,</para>
      </listitem>

      <listitem>
        <para>PEPr proposals get accepted, but no package is registered /
        released.</para>
      </listitem>
    </orderedlist>
  </section>

  <section xml:id="chapters.rfcs.orphan-proposals.solution">
    <title>The solution</title>

    <para>In these 2 cases PEAR QA should step in and try to get in touch with
    the specific proposers. If the proposer is no more interessted in the
    proposal, PEAR QA should search for a new maintainer for the package or
    the proposal should be deleted.</para>

    <para>For these steps the following time frames are proposed:</para>

    <section xml:id="chapters.rfcs.orphan-proposals.solution.unfinished">
      <title>For proposals in stages "draft" and "proposal"</title>

      <itemizedlist>
        <listitem>
          <para>PEAR QA posts a reminder comment to the proposal after
          <emphasis>1 week</emphasis> of inactivity.</para>
        </listitem>

        <listitem>
          <para>If the proposer does not react within <emphasis>2
          weeks</emphasis>, the proposal gets deleted.</para>
        </listitem>
      </itemizedlist>
    </section>

    <section xml:id="chapters.rfcs.orphan-proposals.solution.finished">
      <title>For proposals in stage "finished"</title>

      <itemizedlist>
        <listitem>
          <para>PEAR QA tries to contact the maintainer <emphasis>4
          weeks</emphasis> after the proposal is finished and no release has
          been throwen.</para>
        </listitem>

        <listitem>
          <para>If the maintainer can not be contacted within <emphasis>4
          weeks</emphasis>, PEAR QA starts searching for a new
          maintainer.</para>
        </listitem>

        <listitem>
          <para>If no new maintainer is found within <emphasis>4
          weeks</emphasis>, the proposal gets marked as orphan.</para>
        </listitem>
      </itemizedlist>

      <para>The above stated actions maybe automized inside PEARWeb in future,
      as far as possible.</para>
    </section>
  </section>

  <section xml:id="chapters.rfcs.orphan-proposals.orphanmarker">
    <title>Orphan marker</title>

    <para>Finished proposals should not be deleted, but marked as orphan. This
    marker should have the following content:</para>

    <itemizedlist>
      <listitem>
        <para>To the name of the proposal the following tag will be added:
        "[QA-ORPHAN]".</para>
      </listitem>

      <listitem>
        <para>To the describtion of the proposal the following text will be
        added at the top: <quote>This proposal has been marked orphan by
        PEAR-QA on &lt;DATE&gt; because of the inactivity of the proposer.
        This means, that the proposal is invalid from this date on. If you
        have a similar proposal or want to re-activate this proposal, feel
        free to create a new PEPr proposal for it.</quote>.</para>
      </listitem>
    </itemizedlist>
  </section>

  <section xml:id="chapters.rfcs.orphan-proposals.cleanup">
    <title>Initial cleanup</title>

    <para>To get this process running, an initial cleanup is required. The
    procedure is only run once, when this proposal gets accepted. This cleanup
    should have the following steps:</para>

    <section xml:id="chapters.rfcs.orphan-proposals.cleanup.unfinished">
      <title>Proposals in stages "proposal" and "draft"</title>

      <para>PEAR QA will post a reminder comment to every proposal which shows
      no action since <emphasis>4 weeks</emphasis>. If the proposer is not
      reachable within <emphasis>1 week</emphasis>, the proposal is
      deleted.</para>
    </section>

    <section xml:id="chapters.rfcs.orphan-proposals.cleanup.finished">
      <title>Proposals in stage "finished"</title>

      <para>PEAR QA will try to get in touch with the proposers of every
      proposal which is older than <emphasis>4 weeks</emphasis> and for which
      no package has been registerd, yet. If the proposer is not reachable
      within <emphasis>2 weeks</emphasis>, the proposal is marked as
      orphan.</para>
    </section>
  </section>
</chapter>