On Wed, Dec 18, 2024 at 6:35 PM Clemens Lang <cllang@xxxxxxxxxx> wrote: > > I realized that after I clicked send, but I don’t think it really makes a difference. > The main admin for many of the packages maintained by the crypto team is no longer the person that takes care of the tickets by default. > > For example, Sahana used to maintain stunnel, but I am now the main maintainer. OpenSSL’s officially owned by Sahana, but Dima is doing most of the work. ca-certificates is now by default handled by Frantisek, not Bob. We never bothered changing this in pagure. We shuffle packages around roughly once a year depending on workload and interest. What matters is that somebody reacts to tickets filed against a package, and we do that. In that case, your group is obviously not one of the problematic cases here :) Still, it might make sense to just "give" the packages to the person who currently does the bulk of the maintenance, just so it's clear for people who look at the package who to contact in case going through the group is not possible. Fabio -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
