On Wed, Jun 3, 2026 at 12:06 PM Ankur Sinha <[email protected]> wrote: > > On Wed, Jun 03, 2026 02:22:50 +0000, Packaging Reports wrote: > > python-dandischema @neuro-sig, @python-packagers- 2 weeks > > ago > > python-libsass @neuro-sig, @python-packagers- 2 weeks > > ago > > sig, jonathanspw, orphan > > python-qtsass @neuro-sig, jonathanspw, 2 weeks > > ago > > python-zarr-checksum @neuro-sig, @python-packagers- 2 weeks > > ago > > sig, orphan > > rust-npm-package-json @neuro-sig, @rust-sig, orphan 2 weeks > > ago > > Should we also automatically remove SIGs from packages when they are > only owned by 'orphan'? > > If another SIG member wants to take the package on, we can re-add the > SIG, but without a primary maintainer, having SIGs attached to packages > doesn't do much (as SIG groups cannot be the primary maintainer for > packages). > > Since most SIGs have only commit access to packages too, another SIG > member (like me) cannot remove the SIG from the package either, which > means the package continues to be counted among SIG packages, even after > it has been orphaned. > > In the meantime, how would one request that a SIG group be removed from > a package? An infra ticket?
If the group is only added with "commit" access - yes, need to file a ticket (though this is maybe more a releng than an infra thing). But in general, I don't think groups should be removed. They need to retain access to the package in all non-retired branches. And some groups would get re-added to the package automatically anyway. Fabio -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
