Re: Bugs mailing list

On Nov 1, 2007, at 3:48 PM, Joe Stump wrote:

Do we really have to encourage people to reinvent the wheel instead of improving and working with existing PHP projects (setting aside the "it should be PHP" argument for now) that already exist, that already use some PEAR libs, that use most PEAR-style conventions? The same sentiment showed up on the Zend Framework lists when they first started using trac (which worked much better than their current java-based tools, at least). Not invented here, to the utmost.

+10000 Why not just use what works and just stick to creating world class PHP libraries? I've got extensive experience working with Trac; hacking, modifying, installation, etc. I could have a great setup ready to go in no time. This not invented here syndrome is a bummer.

/me ducks... Didn't mean to start a holy war here guys :-) That said, PHP has zero good bug tracking solutions. I'd go so far to say that there is not a good bug tracking package out there that is really that good. Google Code's issue tracker is nice, but I can't host it myself or customize it beyond the customization they allow. Trac isn't even that good for it in my opinion as it quickly moves towards a cleaned up version of Mantis with SVN/wiki integration. Give me a nice simple bug tracker that stays out of the way and offers good extensibility and I'll be happy to start using it. Seriously. I'm not actually a fan of having to write apps that duplicate the behavior of a dozen other programs simply because they all suffer from <insert favorite problem: feature bloat, not enough features, no extensibility, unusable UI, can't be installed half the time, etc.>. Until then, I'm going to keep wishing there was a decent bug tracker out there, preferably written in PHP. -T