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: LIMBOURG Arnaud [mailto:arnaud.limbourg.prestataire@cegetel.fr] > Sent: Wednesday, August 13, 2003 11:58 AM > I remember somebody telling me that people who have CVS should be able to > commit things. If the maintainer don't like it, cvs is there for a > purpose, > you can always revert. 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. > That said if there are patches waiting for maintainer feedback and no is > provided for a length of time then i think it's ok to commit. There will > be > no release anyway so that won't affect people. Yes but nobody has defined that "length of time". Actually nobody has defined that there is such a "length of time" at all. Regards, Lukas