cvs: peardoc /en/guide/newmaint takingover.xml

mj Thu Dec 15 09:52:35 2005 EDT Modified files: /peardoc/en/guide/newmaint takingover.xml Log: * Redid most of the wording. * Organized the different steps into an ordered list. http://cvs.php.net/viewcvs.cgi/peardoc/en/guide/newmaint/takingover.xml?r1=1.9&r2=1.10&diff_format=u Index: peardoc/en/guide/newmaint/takingover.xml diff -u peardoc/en/guide/newmaint/takingover.xml:1.9 peardoc/en/guide/newmaint/takingover.xml:1.10 --- peardoc/en/guide/newmaint/takingover.xml:1.9 Thu Dec 15 09:34:34 2005 +++ peardoc/en/guide/newmaint/takingover.xml Thu Dec 15 09:52:35 2005 @@ -1,4 +1,4 @@ -<!-- $Revision: 1.9 $ --> +<!-- $Revision: 1.10 $ --> <!-- $Author: mj $ --> <chapter id="newmaint.takingover"> <chapterinfo> @@ -6,37 +6,77 @@ <firstname>Arnaud</firstname> <surname>Limbourg</surname> </author> - <date>$Date: 2005/12/15 09:34:34 $</date> + <date>$Date: 2005/12/15 09:52:35 $</date> </chapterinfo> <title>Taking over an unmaintained package</title> - <titleabbrev>Taking over</titleabbrev> - <simpara> - A package is explicitely marked as unmaintained on <ulink - url="&url.pear;">PEAR website</ulink> and you wish to take over as - new Lead. This short document will explain what steps you need to - take. - </simpara> + <titleabbrev>Taking over a package</titleabbrev> <simpara> - You must first notify the <ulink url="mailto:&email.pear.qa;">PEAR - Quality Assurance mailing list</ulink> to state who you are and what - are your motivations. + If you want to become the new lead maintainer of a package that + is marked as unmaintained on the <ulink url="&url.pear;">PEAR + website</ulink>, the following section will explain to you the + necessary steps for this to happen. </simpara> - <simpara> - The QA team will then state whether you can take over or not - explaining why. You should apply for a <ulink - url="&url.pear.account.new;">PEARweb account</ulink> if you don't - have one. As a next step you will be added as new lead of the - package. In case you do not have a CVS account please <ulink - url="&url.php.cvs.new;">apply</ulink> for one. In any case you must - send a mail to <ulink url="mailto:&email.pear.group;">PEAR - Group</ulink> requesting cvs karma for the package. It is important - you mention you do so with the approval of the QA team. If - possible please add a link to the relevant QA list email, using a - mailing-list archive such as <ulink - url="http://news.gmane.org/gmane.comp.php.pear.qa">GMane</ulink>. - </simpara> + <orderedlist> + + <listitem> + <simpara> + The first thing is to inform the <ulink + url="mailto:&email.pear.qa;">PEAR Quality Assurance mailing + list</ulink> about your intention. If you have not been + involved in PEAR prior to that, it is a good idea to write a few + words about who you are and what your motivations are. + </simpara> + </listitem> + + <listitem> + <simpara> + The QA team will then state whether you can take over the + package or not, eventually explaining why. You can then <ulink + url="&url.pear.account.new;">apply for an account</ulink> for + the PEAR website unless you already have one. The PEAR Group + will have to grant this account, and afterwards the QA team will + assign you as the new lead maintainer for the package. + </simpara> + </listitem> + + <listitem> + <simpara> + If the sources of the package are kept in the PHP CVS + repository, you will also need an account for this. You can + sign up for it on the <ulink url="&url.php.cvs.new;">PHP + website</ulink>. Please mention in the purpose field of the + request form that the PEAR QA team has told you to get an + account, so that your request can be processed faster. CVS + accounts are managed by the PHP Group, so PEAR unfortunately has + only limited influence on this process. + </simpara> + + <note> + <simpara> + In case you already have a CVS account for + <literal>cvs.php.net</literal>, it is only necessary for you + to get additional <quote>karma</quote> for the module where + the package resides. You can request this karma by sending an + email to the <ulink url="mailto:&email.pear.group;">PEAR + Group</ulink>. (Please also mention in this mail that you + have already talked to the QA team.) + </simpara> + </note> + </listitem> + + <listitem> + <simpara> + If everything has worked out well, you should by now be the lead + maintainer of the previously unmaintained package. If not, + don't hesitate to ask the people on the QA mailing list for + help. + </simpara> + </listitem> + + </orderedlist> + </chapter> <!-- Keep this comment at the end of the file Local variables: