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? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London
signature.asc
Description: PGP signature
-- _______________________________________________ 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
