Re: Orphaned packages looking for new maintainers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 15. 04. 21 6:54, Miroslav Suchý wrote:
Dne 12. 04. 21 v 18:32 Miro Hrončok napsal(a):
cura-lulzbot orphan, spot                             6 weeks ago
fedora-jam-kde-theme      jvlomax, orphan 0 weeks ago
gnome-desktop             alexl, caolanm, fmuellner, gnome-sig, 0 weeks ago
                          orphan, rhughes

How this can happen? I.e., orphaned package with one or more co-maintainers.

This is definitively repetitive pattern. I wonder whether we have some process problem?

Why the main admin does not ask co-maintainers first?

I think we get lucky if the no-longer-interested maintainers at least care enough to actually orphan the packages. In most of the cases, they just go AWOL and we wait for non-responsive process / FTBFS / FTI to happen.

In the ideal case, orphanings are reported on devel list and co-maintainers are contacted directly, but that almost never happens. (Anecdata: I've even seen Red Hat associates who maintain package X in RHEL to silently orphan it in Fedora without even being subscribed to devel.)

That's why the co-maintainers are listed in this report and they are Bcced, so they get notified about the situation. As far as process goes, I think that works nicely.

Anyway, gnome-desktop has reason for being orphaned actually listed in pagure:

"Unmaintained upstream -- Nothing currently maintained should use this anymore. A lot of people file general GNOME bugs on this component, thinking it's some catch-all, so a lot of time is spent reassigning bugs to gnome-shell etc."

And if they are not interested in, why they are still listed as co-maintainers?

There are many possibilities:

1. They don't ever read Fedora email.

2. They are gone from Fedora but nobody non-responsive-removed them yet.

3. They are interested in co-maintaining only,
   rather letting the package to be retired than taking the responsibility
   of being the primary contact person for it.

4. They are co-maintainers only for other branches (EPEL or older Fedora)
   (I even sometimes orphan a package and add myself as co-maintainer so I can
    solve the problems in released Fedoras until they all go EOL,
    see for example the case of cura-lulzbot: @spot orphaned it, announced it,
    but he remains a co-maintainer which is completely fine --
    users will report bugs for Fedora 32/33/34).

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux