Re: Bugs mailing list

From: Date: Thu, 01 Nov 2007 21:57:20 +0000
Subject: Re: Bugs mailing list
References: 1 2 3 4 5 6 7 8 9 10 11  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-48385@lists.php.net to get a copy of this message
till wrote:
On 11/1/07, Joshua Eichorn <josh@bluga.net> wrote:
Joe Stump wrote:
    
Didn't mean to start a holy war here guys :-)
Not a holy war. I'm just forgetting that Open Source is a bureaucracy
as opposed to a business. This is so far outside of the scope of what PEAR's *core competency* is it's amazing it's even being discussed to me. In fact, it's been disallowed that *applications* be created, submitted and distributed via PEAR for some time now (the exception being pearweb; even the PEAR channel code is on a separate channel). What I'm saying is, as a consumer of PEAR, I find it sad that brilliant, core PHP developers are proposing chasing the bug tracker holy grail rather than making me cool ass PHP libraries. As a lazy PEAR developer I'm saying have fun; I'll be sticking to creating more PEAR code for now. With that I'm out. --Joe
      
I'll agree with not spending time on a bug tracker, but we already have one. And any change is going to be a lot of work, so lets just stick with the current one. Anything else we pick will be just as bad (you only like tools until you use them).
    
Rumour has it that the current one will be replaced anyway? Someone said Jani and Greg are working on a new one. It could be as simple as a vote if people want trac. My last 2 cents. Till Yes but that means Jani will be planing to import current bugs from the start. Trac means someone has to install it, set it up, make it work with pearweb logins, import all current bugs, find a place to host it. Thats a little more work then a new version of the current bug tracker. -josh

« previous php.pear.dev (#48385) next »