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

> From: Derick Rethans [mailto:derick@php.net] > Sent: Wednesday, August 13, 2003 12:56 PM > On Wed, 13 Aug 2003, Lukas Smith wrote: > > > No. The users can do to bugs and find the patch and apply it. What if > > one fix conflicts with another etc? This is all stuff that requires good > > knowledge of the package. However that is not even the point. The point > > is that the developers of the package have the ultimate control over the > > package as the PEAR rules stand now. There are already some limits in > > the for of the PEAR CS etc. And we may want to expand these. Like > > introduce a minimal turn around time which if not met *could* result in > > some body (the community, pear group, pear qa .. ) to be defined to give > > commit rights to someone. > > I wouldn't go into the "minimal turn around time", as there might be > plenty of very good reasons why a developer doesn't answer. I don't see > anything wrong with the current rules. The package is the developer's > responsibility, other people shouldn't touch it (without approval) of > that developer. (This is also one of the reasons xdebug is not in PECL > CVS btw). This is not a sufficient solution. Bugs have to be fixed! Packages cannot linger forever without them being expanded to cover our needs if such needs come up. Period. There is no arguing around it. There are a few ground rules we have that make this necessary. We are not hot script ... when putting in your code you accept certain responsibilities not the least of which is code quality. Regards, Lukas