cvs: peardoc /en/guide/newmaint proposal.xml when-to-contribute.xml

From: Date: Tue, 13 Jul 2004 20:53:03 +0000
Subject: cvs: peardoc /en/guide/newmaint proposal.xml when-to-contribute.xml
Groups: php.pear.doc 
Request: Send a blank email to pear-doc+get-4591@lists.php.net to get a copy of this message
mj Tue Jul 13 16:53:03 2004 EDT Modified files: /peardoc/en/guide/newmaint proposal.xml when-to-contribute.xml Log: * Changed the different flavours of the term "mailing list" (which included "list", "mailinglist" and "mailing list") to the consistent and correct "mailing list". http://cvs.php.net/diff.php/peardoc/en/guide/newmaint/proposal.xml?r1=1.14&r2=1.15&ty=u Index: peardoc/en/guide/newmaint/proposal.xml diff -u peardoc/en/guide/newmaint/proposal.xml:1.14 peardoc/en/guide/newmaint/proposal.xml:1.15 --- peardoc/en/guide/newmaint/proposal.xml:1.14 Tue Jul 13 16:50:57 2004 +++ peardoc/en/guide/newmaint/proposal.xml Tue Jul 13 16:53:03 2004 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.14 $ --> +<!-- $Revision: 1.15 $ --> <chapter id="newmaint.proposal"> <chapterinfo> <author> @@ -10,7 +10,7 @@ <firstname>Tobias</firstname> <surname>Schlitt</surname> </author> - <date>$Date: 2004/07/13 20:50:57 $</date> + <date>$Date: 2004/07/13 20:53:03 $</date> </chapterinfo> <title>The formal proposal process</title> <titleabbrev>Proposing</titleabbrev> @@ -18,9 +18,9 @@ <simpara> In the early times of PEAR, all new packages were proposed by an informal email to the <ulink url="mailto:&email.pear.dev;">PEAR - developers list</ulink>. Over the time, the number of new proposals - increased quite dramatically, making it hard to keep track of all the - proposals. + developers mailing list</ulink>. Over the time, the number of new + proposals increased quite dramatically, making it hard to keep track + of all the proposals. </simpara> <simpara> A web-ased proposal handling system was established to solve these @@ -233,7 +233,7 @@ Votes</quote> and <quote>Finished</quote>. Every proposal has to run through all of these stages. During each stage (except for the draft stage) an email is send to you (the proposer) and the <ulink - url="mailto:&email.pear.dev;">PEAR developer mailinglist</ulink> + url="mailto:&email.pear.dev;">PEAR developer mailing list</ulink> for any action. </para> @@ -334,7 +334,7 @@ In general you may not edit or delete your proposal after it has left the Proposal stage. In urgent cases you can contact the PEAR community via the <ulink - url="mailto:&email.pear.dev;">developers list</ulink> to + url="mailto:&email.pear.dev;">developers mailing list</ulink> to reach a PEAR website administrator to do a change. This is heavily discouraged however! You should have made everything clear to the community during the Proposal stage to ensure a hassle free voting http://cvs.php.net/diff.php/peardoc/en/guide/newmaint/when-to-contribute.xml?r1=1.5&r2=1.6&ty=u Index: peardoc/en/guide/newmaint/when-to-contribute.xml diff -u peardoc/en/guide/newmaint/when-to-contribute.xml:1.5 peardoc/en/guide/newmaint/when-to-contribute.xml:1.6 --- peardoc/en/guide/newmaint/when-to-contribute.xml:1.5 Thu Jun 17 04:30:32 2004 +++ peardoc/en/guide/newmaint/when-to-contribute.xml Tue Jul 13 16:53:03 2004 @@ -1,12 +1,12 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.5 $ --> +<!-- $Revision: 1.6 $ --> <chapter id="newmaint.when-to-contribute"> <chapterinfo> <author> <firstname>Martin</firstname> <surname>Jansen</surname> </author> - <date>$Date: 2004/06/17 08:30:32 $</date> + <date>$Date: 2004/07/13 20:53:03 $</date> </chapterinfo> <title>When to contribute (and when not to contribute)</title> <titleabbrev>When to contribute</titleabbrev> @@ -16,7 +16,7 @@ contribute code to PEAR and in which it does not. This description is by no means complete. If you are unsure, if your contribution could be included into PEAR, contact the <ulink - url="mailto:&email.pear.dev;">developers mailinglist</ulink>. + url="mailto:&email.pear.dev;">developers mailing list</ulink>. </simpara> <sect1 id="newmaint.when-to-contribute.good">

« previous php.pear.doc (#4591) next »