Bug #4207 [Asn->Csd]: "Contradictions" in the manual formal proposal process-wise
| From: | arnaud@php.net | Date: | Thu, 06 Oct 2005 09:05:44 +0000 |
| Subject: | Bug #4207 [Asn->Csd]: "Contradictions" in the manual formal proposal process-wise | ||
| References: | 1 | Groups: | php.pear.doc |
| Request: | Send a blank email to pear-doc+get-6979@lists.php.net to get a copy of this message | ||
Edit report at http://pear.php.net/bugs/bug.php?id=4207&edit=1
ID: 4207
Updated by: arnaud@php.net
Reported By: pear at sf dot rausch-e dot net
-Status: Assigned
+Status: Closed
Id: 4207
Type: Bug
Package: Documentation
PHP Version: Irrelevant
Assigned To: mj
New Comment:
This bug has been fixed in CVS.
If this was a documentation problem, the fix will appear on
pear.php.net by the end of next Sunday (CET).
If this was a problem with the pear.php.net website, the change should
be live shortly.
Otherwise, the fix will appear in the package's next release.
Thank you for the report and for helping us make PEAR better.
Previous Comments:
------------------------------------------------------------------------
[2005-06-12 05:21:43] mj at php dot net
The common way these days is to immediately start a proposal in PEPr.
If nobody objects, I'm going to reflect this in the documentation some
time soon.
------------------------------------------------------------------------
[2005-04-22 17:33:15] pear at sf dot rausch-e dot net
Description:
------------
The PEAR manual should clearify the official (true one) approach to
follow proposal-wise or at least state that both ways are viable -
statement consistency in both of the following chapters:
http://pear.php.net/manual/en/newmaint.proposal.step2.php
Chapter 10.
The formal proposal process - Step 2: Initiating a discussion
Before starting the proposal process in PEPr, a thread should be
started for each new package on the developers mailing list. This
intermediate step is preferred for the sake of convenience, because it
is easier and more comfortable for us to hit a single key in our mail
client to join a discussion than to open a browser window and look up
the right page on the website...
is somehow in contradiction with
http://pear.php.net/manual/en/developers.contributing.howto.php
Chapter
13. Contributing your own code. How to contribute code in practice - 2.
Announcing to the PEAR developers
The second step while contributing is to announce your package in PEPr.
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...
Which is the correct way to go: PEAR-Dev and/or PEPr?
------------------------------------------------------------------------
--
Edit this bug report at http://pear.php.net/bugs/bug.php?id=4207&edit=1