[PEPr] -1 for RFC::Prefix all classes with PEAR_
| From: | Jesus M. Castagnetto | Date: | Thu, 05 Oct 2006 16:41:29 +0000 |
| Subject: | [PEPr] -1 for RFC::Prefix all classes with PEAR_ | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44367@lists.php.net to get a copy of this message | ||
Jesus M. Castagnetto (http://pear.php.net/user/jmcastagnetto) has voted -1 on the proposal for
RFC::Prefix all classes with PEAR_.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=420
Vote information:
http://pear.php.net/pepr/pepr-vote-show.php?id=420&handle=jmcastagnetto
Comment:
As other pointed out. Pushing this proposal a this time is not the best
thing. Even if the proposal means well, it has a scope that is way to wide
for its intent. Trying to make all existing packages conform to this is not
practical, not to mention confusing and not woth the effort at the moment.
Also, there is no consideration as to the mechanism to accomplish all what
it proposes. Who is going to do it? What is the timeline for accomplishing
this? Who is going to do QA for this process?, etc.
Personally, I'd rather have a more complete discussion how are we going to
move for the next stage of PEAR, and how are we going to build the
infrastructure of people and resources to get there.
Wouldn't it be better to re-propose this RFC when things are a bit
clearer? It will be better than having something that is hardly
enforceable or doable, and will just gather dust and perhaps will need
another RFC to modify or revoke.
--
Sent by PEPr, the automatic proposal system at http://pear.php.net