#418 Packager jgarzik violated Fedora Packaging (Review) Policy
Closed None Opened 13 years ago by robert.

Packager "jgarzik", a Red Hat employee, recently violated the Fedora Packaging (Review) Policy by closing various "Merge Review" bug reports inside of the Red Hat Bugzilla for the Fedora component - but without any formal/official review; some of them he even set fedora-review+.

Examples:

As I expect a packager to know the Fedora policies, I'm expecting hereby FESCo now to downgrade jgarzik's permissions in Red Hat Bugzilla for Fedora component. I'm not sure, but I assume "fedorabugs" group membership gave him the ability to have enough permissions in bugzilla for such actions.

Additionally, Red Hat has to ensure that Red Hat employees follow the Fedora rules; which doesn't seem to be the case right now (I'm thinking about the "perl*" thing). Is that all because Red Hat is Red Hat and doesn't want to care about Fedora rules?


We can discuss this at the next meeting, but I don't see the need to censure in this case.

He thought he was cleaning up old unneeded tickets to help the review queue.
He now knows he should leave those alone.

Everyone makes mistakes, I think we shouldn't focus so much on punishing people, and instead work on educating and praising people when they do good.

All just IMHO. We can surely discuss at the next meeting.

Somebody needs to ensure, that especially Red Hat people are educated properly.

Robert, please stop. Your own conduct in bug 226440 was anything but excellent, and now you continue to spew vitriol against Red Hat people in this FESCo ticket.

While I agree that Roberts behavior in bug 226440 was offensive and inadequate I think he is right that Red Hat people need more education about the Fedora guidelines. Red Hat people have violated Fedora's guidelines in the past and still do so, in fact I think these incidents have become more frequent recently (think of the perl mass-acl change).

More education would be great. Punishing anyone is IMHO counterproductive especially when people have been educated since the action.

The "perl mass-acl change" was not particular to Red Hat IMHO. It could have happened to anyone else and we now have a process in place to prevent it happening again.

Replying to [comment:5 kevin]:

The "perl mass-acl change" was not particular to Red Hat IMHO. It could have happened to anyone else and we now have a process in place to prevent it happening again.

The two "maintainers" were Red Hat employees and so was their sponsor. I can give you a more examples where RH folks ignored guidelines and threw over the community, but in this particular case I think that jgarzik had no bad intentions when he closed the bugs. Nevertheless it shows that he doesn't know the rules and procedures well enough.

FESCo declined to censure here. Education and what to do about merge reviews are still open topics. Continue discussion of those on the devel list until we have concrete proposals.

Login to comment on this ticket.

Metadata