cvs: peardoc /en/guide/developers contributing.xml

From: Date: Sun, 25 Jan 2004 10:53:06 +0000
Subject: cvs: peardoc /en/guide/developers contributing.xml
Groups: php.pear.doc 
Request: Send a blank email to pear-doc+get-2152@lists.php.net to get a copy of this message
toby Sun Jan 25 05:53:06 2004 EDT Modified files: /peardoc/en/guide/developers contributing.xml Log: * Changes for PEPr usage. http://cvs.php.net/diff.php/peardoc/en/guide/developers/contributing.xml?r1=1.15&r2=1.16&ty=u Index: peardoc/en/guide/developers/contributing.xml diff -u peardoc/en/guide/developers/contributing.xml:1.15 peardoc/en/guide/developers/contributing.xml:1.16 --- peardoc/en/guide/developers/contributing.xml:1.15 Wed Oct 8 16:35:20 2003 +++ peardoc/en/guide/developers/contributing.xml Sun Jan 25 05:53:06 2004 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.15 $ --> +<!-- $Revision: 1.16 $ --> <!-- WORK IN PROGRESS, THERE IS PROBABLY LITTLE POINT IN TRANSLATING THIS DOCUMENT YET. @@ -229,14 +229,14 @@ <simpara>Announcing to the PEAR developers</simpara> <para> - The second step while contributing is to announce your package on - the <ulink url="mailto:&email.pear.dev;">developers mailing list</ulink>. - Usually this announcement will spawn some discussion and the - developers will then start to vote for or against your proposal. - (You are of course urged to join the upcoming discussion.) - Announcing a package does of course not mean that it is already - accepted! That will still take some time and likely some more - efforts from your side. + The second step while contributing is to announce your package in + <ulink url="http://pear.php.net/pepr/">PEPr</ulink>. + Usually this announcement will spawn some discussion. After one week + you may call for votes with PEPr and the developers will then + start to vote for or against your proposal. (You are of course + urged to join the upcoming discussion.) Announcing a package does of + course not mean that it is already accepted! That will still take + some time and likely some more efforts from your side. </para> <note> <para> @@ -252,7 +252,7 @@ <para> Only the votes of active members of the PEAR community (must have a PEAR web account, however the proposer himself is not counted) - are counted, however anyone may vote. Votes require that a final + are counted, however anyone may vote. Votes require that a final choiceof package name is specified. </para> <para> @@ -272,13 +272,13 @@ </para> <para> - In case the proposal is not accepted the package can be further + In case the proposal is not accepted the package can be further discussed on the list and the proposer may attempt to make another "call for vote" (it is expected that this is only done for sensible reasons). </para> </listitem> - + <listitem id="developers.contributing.accounts"> <simpara> Getting the necessary accounts @@ -297,7 +297,7 @@ your package through PEAR. With this account you have access to the necessary infrastructure on <ulink url="&url.pear;">pear.php.net</ulink> in order - to upload and roll new releases.</para> + to propose, upload and roll new releases.</para> </listitem> <listitem>

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