This is a follow up from a request that was opened against the infrastructure at: https://pagure.io/fedora-infrastructure/issue/8600 and discussed a little bit on the devel list: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/K5V3GMFQ7AVLSXLWGRAI5CLF5ZFU54KX/
The gist of it is: do we want to remove all the co-maintainers of a package once that package has been retired on all branches (ie: Fedora and EPEL).
I know some people asked to see the script used on the devel list, so here it is. I'll likely be ported to https://pagure.io/fedora-infra/toddlers and be set to run regularly (I am thinking weekly).
<img alt="retired_packages_with_maintainers.py" src="/fesco/issue/raw/files/974fac7a8404fffca339f51968be60a18643a43a4be639a5f2747adac3f0785b-retired_packages_with_maintainers.py" />
I think this is a good idea to reduce noise and cognitive burden for everyone involved.
I'm not sure that running this weekly is necessary - the points in time where most changes will occur are probably the EOL dates for "oldstable" fedora branches (when the last "maintained" branch falls off the cliff). That doesn't account for EPEL branches, though ...
I think this is a good idea to reduce noise and cognitive burden for everyone involved. I'm not sure that running this weekly is necessary - the points in time where most changes will occur are probably the EOL dates for "oldstable" fedora branches (when the last "maintained" branch falls off the cliff). That doesn't account for EPEL branches, though ...
The frequency can be tuned to say: the 1st and 15th of the month, but honestly at that point we're bikeshedding :)
The script takes about 22 minutes from my laptop which has an ocean between it and the data-source (I should test it closer to the source to get a better idea).
Do it +1.
I'm good with this as well.
+1
So, just to add some background here... it was intentional that we left maintainers on packages when orphaned. The idea was that if they were just away/busy/whatever they might come back later and jump right back in helping out. It may be that just contacting the new maintainer to be re-added would be sufficent for that now.
The other problem might be for historical notes... perhaps someone wants to revive a retired package and wants to ask former maintainers why it was retired, they don't have a super easy way to see who those people were. I guess they can look at changelogs and koji build's, but it is a bit harder. We should also note this in the 'bringing a package back from retirement' docs...
I'm +1 I guess, but we should note the changes in any docs. :)
This has been APPROVED (+6,0,-0) for a while.
Metadata Update from @churchyard: - Issue tagged with: pending announcement
I don't know very well FESCo's processes, may I proceed with this change now, or should I wait for it to be announced?
You can proceed now.
Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NHIKO64AWRW72LEOD3LMJ5E6FJT62CED/
Metadata Update from @decathorpe: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.