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())

On Wed, 13 Aug 2003, Lukas Smith wrote: > > 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. Of course not, but forever is something of a different order than "two weeks". > 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. Sure, and to be able to use that responsibility you need full control over your stuff to, you can not have a lot of other people screwing with your code, not even if you're away for a one month holiday. Derick -- "Interpreting what the GPL actually means is a job best left to those that read the future by examining animal entrails." ------------------------------------------------------------------------- Derick Rethans http://derickrethans.nl/ International PHP Magazine http://php-mag.net/ -------------------------------------------------------------------------