commiting bug fixes to other peoples packages (was RE: [PEAR-DEV] #25060 [NEW]: Math_Integer/Integer/gmp.php uses raisError() instead of raiseError())

From: Date: Wed, 13 Aug 2003 09:22:29 +0000
Subject: commiting bug fixes to other peoples packages (was RE: [PEAR-DEV] #25060 [NEW]: Math_Integer/Integer/gmp.php uses raisError() instead of raiseError())
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-19655@lists.php.net to get a copy of this message
> From: nicos@php.net [mailto:nicos@php.net] > Sent: Wednesday, August 13, 2003 1:41 AM > > "Greg Beaver" <greg@chiaraquartet.net> a écrit dans le message de > news:3F397A02.6030405@chiaraquartet.net... > > > > > > Stefan Neufeind wrote: > > > > > just to understand "how it works" on pear generally: > > > why you filed a bug? > > > wasn't it corrected in cvs? if not: why didn't you simply submit a > > > patch to cvs? > > I filed a bug because I was looking at CVS, not release, and I didn't > > fix it because I am not a developer or maintainer of the package I > > mentioned, and the developer would not be very pleased to find that > > random people are correcting his/her code without warning :). > Greg, I agree that you shouldn't commit it, but please, If you don't get > any > feedback after 2 weeks, please commit if you're sure of you. > I have like 20 patchs that are waiting for feedbacks since 1 month and I > will commit them if I don't get any very soon. I start to be bored of this > stupid law, > I will not leave a bug open only because the maintainer doesn't answer > and > that he doesn't care of the package. Even more if I'm sure it fixes the > problem. I applaud your recent efforts to eliminate bugs in PEAR packages. However currently we have no regulations dealing with when other people are allowed to commit fixes to packages that they are not responsible for. Actually currently there is only the regulation that package developers are solely responsible. Don’t get me wrong. I am in favour of adding regulations that will allow people to commit those bugs fixes. However this will only be done if developers are unreachable for a longer period of time (certainly more than 2 weeks) and it will not be a decision up to a single person. I think pear group should be responsible for this for now. In the long terms I would rather have pear qa (once this group of people are off and running) be the group to decide on this. Regards, Lukas

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