Mastering Bug Monitoring for Fedora GNOME Packages: A Practical Guide

Overview

For years, users reporting bugs against GNOME packages in Fedora received an automated response stating that their report was not actively monitored and encouraging them to file the bug upstream with GNOME instead. This practice, however, ran counter to the Fedora Engineering Steering Committee (FESCo) policy requiring package maintainers to “deal with reported bugs in a timely manner.” On April 28, FESCo discussed this disconnect and decided to adjust the wording of the automatic reply. This guide explains the policy, the auto-reply issue, and how maintainers can align their bug-monitoring workflow with Fedora’s expectations.

Whether you are a Fedora contributor, a GNOME packager, or a user who wants to understand the process, this article provides clear steps, common pitfalls, and best practices. By the end, you will know how to configure auto-replies, interpret FESCo’s requirements, and ensure your bug tracking is both efficient and policy-compliant.

Prerequisites

Before diving into the steps, you should have:

• Basic familiarity with Bugzilla or the bug tracker used by Fedora (Red Hat Bugzilla).
• Understanding of Fedora’s package maintenance workflow – including the difference between upstream (GNOME) and downstream (Fedora) bug reports.
• Access to a Fedora package maintainer account (or the ability to view the auto-reply configuration for a component).
• Knowledge of FESCo policies – particularly the policy on bug handling (FESCo #1234, as referenced in discussions).

Step-by-Step Instructions

1. Understanding FESCo’s Policy on Bug Handling

The Fedora Engineering Steering Committee (FESCo) explicitly states that package maintainers must “deal with reported bugs in a timely manner.” This means every bug filed in the Fedora tracker must be acknowledged, triaged, and either fixed or forwarded to the upstream project (like GNOME) without unnecessary delay. The policy does not allow maintainers to simply ignore bugs or delegate all responsibility to upstream.

Key points from the policy:

• Acknowledge the bug within a reasonable timeframe (usually a few days).
• Assess whether the bug is Fedora-specific or a general upstream issue.
• If upstream, inform the reporter and cross-reference the upstream tracker.
• If Fedora-specific, work on a fix or escalate within the Fedora team.

The auto-reply that previously told users “not actively monitored” violated this spirit because it implied the Fedora tracker was not a valid place for bug reports. The FESCo discussion on April 28 aimed to resolve this conflict by adjusting the wording without changing the underlying workflow.

2. The Auto-Reply Issue: Why It Was a Problem

For GNOME packages in Fedora, users who filed a bug would receive an email like:

“This bug report is not actively monitored. Please file your bug upstream at https://gitlab.gnome.org/…”

While this message intended to reduce duplicated effort, it inadvertently discouraged users from reporting bugs through Fedora’s official channel. Moreover, it contradicted the FESCo policy, making the Fedora tracker appear unresponsive. The solution was not to remove the auto-reply entirely, but to rephrase it so that it aligns with the policy while still directing users to the correct upstream location.

3. Adjusting the Auto-Reply Wording

As a maintainer of a GNOME package in Fedora, you can update the auto-reply template for your component. Here is how to do it in Bugzilla (Red Hat instance):

1. Log into Bugzilla with your maintainer account.
2. Navigate to the component’s settings (e.g., Components › gnome-shell).
3. Find the “Auto-Reply Template” field (or similar). This may be under “Component Defaults”.
4. Replace the old text with a policy-compliant version, such as:
   

   Thank you for filing this bug. Your report is important — it helps us improve GNOME on Fedora. Please note that this component is maintained in close coordination with the upstream GNOME project. If this issue is not specific to Fedora, we may ask you to file it upstream at https://gitlab.gnome.org/GNOME/<component>. We will triage this report and provide further guidance soon.

5. Save the changes.

Jump to Common Mistakes for typical errors when crafting such templates.

4. Monitoring Bugs Effectively

After updating the auto-reply, you need to ensure real monitoring happens. Follow this workflow:

• Set up triage rules: Use Bugzilla’s automated assignment or a mailing list to receive new bugs immediately.
• Respond within 48 hours: Acknowledge the bug, even if only to say it is being evaluated.
• Cross-reference upstream: If the issue exists in GNOME, add a comment with the upstream bug URL and set the “Upstream” keyword.
• Track Fedora-specific fixes: For packaging issues (e.g., dependency conflicts, patches), handle them in Fedora’s infrastructure (e.g., Koji, Bodhi).
• Close or redirect: If the bug is fully upstream, close the Fedora report after linking to the upstream tracker. If it is a duplicate, mark accordingly.

By following this process, you comply with FESCo’s “timely manner” requirement while still leveraging upstream development resources.

Common Mistakes

Mistake 1: Using Off-Putting Language

The old auto-reply said “not actively monitored,” which made users feel their report would be ignored. Avoid any phrasing that suggests the Fedora tracker is a dead-end. Instead, emphasize that the report will be reviewed.

Mistake 2: Forgetting to Update All Components

A common oversight is only updating the auto-reply for one GNOME package, while others (e.g., gedit, evince) still have the old template. Ensure all your maintained components are revised. Use Bugzilla’s bulk update feature if you manage multiple packages.

Mistake 3: Failing to Actually Monitor

Revising the auto-reply is not enough — you must commit to regular bug triage. Set calendar reminders or use automation tools like bugzilla2fedmsg to receive notifications.

Mistake 4: Confusing Upstream with Downstream Responsibilities

Some maintainers send every bug upstream without proper triage. Evaluate each report: if it is a packaging bug (e.g., missing dependency in Fedora), fix it yourself. If it is a genuine upstream issue, still handle the Fedora report by providing a link and closing only after upstream confirms.

Summary

Aligning bug-monitoring practices with FESCo policy requires replacing passive auto-replies with proactive, policy-compliant messages, and then actually triaging bugs promptly. By adjusting the auto-reply wording and adopting a clear monitoring workflow, Fedora GNOME package maintainers can resolve the disconnect between policy and practice. This guide has provided the steps to update your Bugzilla templates, a workflow for bug handling, and common pitfalls to avoid. The result: a more responsive Fedora bug tracker that still leverages upstream GNOME development — meeting both user expectations and FESCo requirements.