On Wed, Dec 18, 2024 at 10:43:33AM +0100, Vít Ondruch wrote: > I would object! We've been there prior we arrived to the current workflow. > And the typical situation was that such package was moved from one > non-responsive maintainer to the other non-responsive maintainer. With my > handle beginning with "v" I was always the last to become the maintainer and > I can telly you, waiting or actively calling out other inactive maintainers > is PITA. I don't think there is any big issue with the current situation. > There is 7 weeks for folks to figure that somebody could pick up orphaned > package. I don't accept that co-maintainers are (or should be assumed to be) "typically" non-responsive. That is a depressing denigration of many Fedora co-maintainer's work. Yes, there will be cases where a co-maintainer is not responsive, but we shouldn't design our policy to assume our maintainers are doing a bad job by default. The situation described where there are 2 (or more) co-maintainers and the tool re-assigned to a sub-optimal choice, is precisely why we should NOT designate a single person as the "main admin" (owner). If all maintainers are equal peers, we would not have got into a situation where the maintainer whose name is later in the alphabet gets overlooked as the "best" choice for re-assignment. We cna't solve this with Pagure without dev work, but hopefully our new forge will solve this problem. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- _______________________________________________ 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
