Re: How to make a call for vote with PEPR
| From: | Greg Beaver | Date: | Sun, 06 Jun 2004 14:55:57 +0000 |
| Subject: | Re: How to make a call for vote with PEPR | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-30043@lists.php.net to get a copy of this message | ||
Dmitry Koteroff wrote:
DC> I personally think that there is no such a thing that "code clear DC> enough without any comment". Agreed. But before commenting I need to know that is not useless - if proposal will be declined...PEAR is not about fame. It is about good code. If you don't write good code, it won't be accepted. Documentation is essential to good code, so you're essentially saying "But before writing good code, I need to know that it will be accepted into PEAR." In the past, PEAR accepted any code idea, but this has proven to be a major problem, as many packages simply have not been developed after being accepted, because their maintainers stopped working once the package was accepted. The new standard is to require great, working, complete final-release quality code and then subject it to rigorous QA requirements prior to declaring it stable. If your code is useful, it will be used, don't worry about PEAR, that's just a label, there are plenty of code repositories or project hosting sites (phpclasses, sourceforge, dotgeek) that will be happy to accept your code no questions asked, and once it has matured further, you can always re-propose. Or, you can add comments now and skip all of these steps. I think commenting is a bit easier, personally :) Greg