Hi all, I'm a bit concerned by the headlong rush to refactor phpbugsweb to include PEAR and PECL bugs. The concept is fine by me, but starting with phpbugsweb as the starting point is a big mistake if you plan to include PEAR bugs. The PEAR bug tracker has several killer features that you will have to pry from my cold dead fingers before I would accept a merge with the phpbugsweb
1) patch tracker complete with versioned patches 2) roadmap support with auto-generation of package.xml based on closed bugs/features 3) limited-privilege accounts eliminate the need for CAPTCHA altogether (all you need is the ability to check email and fill in a form with name and password after the fact). We haven't had any spam bugs since implementation and it is more handicapper-accessible. http://pear.php.net/bugs/report.php?package=PEAR_ErrorStack to see an example, all that is required is a valid email address and the ability to add or subtract numbers between 1 and 100 The main problem with the codebase of pearweb/bugs is that it depends on the core of pearweb (bad) and so needs to be independentized, but we are doing this ASAP. roadmap for the website is at http://pear.php.net/bugs/roadmap.php?package=pearweb Of course, it's also in the process of being refactored along with the rest of pearweb (unit tests *gasp*) so please don't discount a look at this codebase, no matter how bigoted against PEAR you might be ;) Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
