fesco

#2206 Clarification needed: Nonresponsive policy for packages with custom Bugzilla assignee (SIG)
Closed: Invalid by churchyard. Opened by churchyard.

Closed: Invalid
Reopen Issue

When a package is technically "owned" (main admin) by an user, yet the default Bugzilla assignee is a group (SIG), do I strat nonresponsive maintainer for the SIG or for the user?

Functionally, it would be mostly the same thing. The main admin is the one that will ulitmately get orphaned. I'd start it for both (CCing both the main admin and the SIG) and then if there is no response, just go ahead and orphan it.

If someone else from the SIG picks it up, great.

+1 to @sgallagh.

+1 to @sgallagh

I don't think this needs a formal vote, thanks for clarification. If somebody disagrees with what was said, feel free to reopen.

Metadata Update from @churchyard:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

Closed invalid as in: works for me.

Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.