On 4/11/06, Michael Schwendt <bugs.michael@xxxxxxx> wrote: > Will it avoid incidents like this? > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187714 Jeff isn't the rpm package maintainer for Core, so I'm not sure how package policy for Core can prevent situations with regard to how he or any other "upstream" developer on a codebase decides to use their bugzilla access. Whether or not Jeff should be closing out bugs like this is something you'll need to discuss with Jeff. Remember that pretty much every contributor has the ability to close out any bugreport.. not just the maintainers of a particular package. So if someone else other than the maintainer closes the bug out, you are free to reopen it and ask them to let the package maintainer decide to close it. The idea is to make it easier for other people to help out with janitorial work.. but that amount of open access will lead to disagreements which are not born of malice or even thought. The line between maintainer and upstream issue can be mis-drawn. In this particular case Jeff is using his bugzilla access to drive things upstrea, and if you feel he's closed the bug in error, reopen it. > Do Core package maintainers accept the current FE packaging guidelines? Or > will reviews result in lengthy discussions about personal preferences? Do all the Extras maintainers accept the current FE packaging guidelines? The guidelines are a living document and discussion among Extras maintainers still happens with regard to the merit of some of the required review items.. As long as the Core release team are prepared to crack the whip and to make the review requirements a requirement for all new packages..Core maintainers will have to accept it as policy. For things which are already in Core I know, based on discussion with some maintainers that they are willing to submit to a review and fix things as manpower and time allow. I'm sure those feelings are shared by all maintainers, especially those that are less active in Extras and/or community facing discussions generally. But you have to start somewhere to build up a culture change inside Core. -jef
