Package Maintainer Responsiblities vs. unmonitored Bugzilla components for GNOME packages

Personal opinion, not speaking for FESCo:

I understand that the amount of bugs that are filed against some of these components is ridiculous, and that the auto-responder that was set up for most GNOME packages was supposed to help with this.

But I don’ think the auto-responder has actually helped at all. Bugs are still being filed - likely at least in part because there’s no indication that you’re filing a bug against a component where you’ll just get a “go away” auto-response. Additionally, once the form is filled and submitted, people likely feel like their “work” is already done, and then they’re asked to go do all that again somewhere else.

The auto-response text also explicitly says that downstream / packaging bugs and / or bugs for release tracking purposes should remain open, but also

Bug reports for this component on Red Hat Bugzilla are not actively monitored

which sounds like a “have your cake and eat it too” situation. If valid downstream / packaging bugs should remain open, then bugs for these components also must be monitored, otherwise keeping these kinds of bugs open is just pointless.

IMO even having the auto-responder auto-close issues and asking people to reopen bugs for downstream / packaging-only issues would be better than the status quo. That way at least the signal / noise ratio of OPEN bugs for these packages / components should be way better, and actively monitoring them would be a lot easier.

2 Likes