Chris Gianelloni kirjoitti: > More and more, I am finding developers who are afraid to touch packages > for even minor things if they're not the maintainer. This is a sad > state of affairs and not the reason we have maintainers. We have > maintainers to assure that a package is being taken care of, not to > establish some kind of "territory" over that package. Because of this > misconception, I would like to come up with and document a listing of > things that any ebuild developer can feel free to do to any package > *without* maintainer consent. These are generally all minor things, but > things that I think are important. I'm going to list off the things > that I can think of, and encourage everyone else to speak up if I've > missed something. >
I don't find anything wrong with doing the changes after you find that the maintainer is not responsive. If the maintainer is responsive, he will a) do the changes b) give you the permission to do it c) give reasoning on why the proposed changes should not be done. Regards, Petteri
signature.asc
Description: OpenPGP digital signature
