<div dir="ltr"><div>I've asked Peter to add me as a maintainer to some of the packages listed above.</div><div><br></div><div>sugar-presence-service was only used by etoys-sugar package which has now been retired.</div><div>webkitgtk4 is now webkit2gtk3 and is still being maintained.<br> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 12, 2020 at 6:14 PM Alex Perez <<a href="mailto:aperez@alexperez.com">aperez@alexperez.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div> <pre>FYI. See below e-mail. There may be others in the list that I'm unaware of. Ibiam, we should probably get you set up as a maintainer for the sugar packages listed below: Here's a curated list of packages that are/may be relevant to us/SoaS: rpms/sugar-analyze is retired but does not list 'orphan' in its users rpms/sugar-analyze is retired and has the following: 'maintainers': pbrobinson, tuxbrewr, callkalpa rpms/sugar-help is retired but does not list 'orphan' in its users rpms/sugar-help is retired and has the following: 'maintainers': pbrobinson, callkalpa rpms/sugar-presence-service is retired and has the following: 'maintainers': pbrobinson, tomeu</pre> <pre>rpms/webkitgtk is retired but does not list 'orphan' in its users rpms/webkitgtk is retired and has the following: 'maintainers': pwalter, kevin, tpopela, huzaifas, mso rpms/webkitgtk3 is retired but does not list 'orphan' in its users rpms/webkitgtk3 is retired and has the following: 'maintainers': phatina, mclasen, pwalter, tpopela 'groups': @gnome-sig rpms/webkitgtk4 is retired but does not list 'orphan' in its users rpms/webkitgtk4 is retired and has the following: 'maintainers': tpopela, kalev, catanzaro 'groups': @gnome-sig</pre> <br> <br> <span> </span><br> <blockquote type="cite" style="border:0px none"> <div style="margin:30px 25px 10px"><div style="display:table;width:100%;border-top:2px solid rgba(146,154,163,0.7);padding-top:10px"> <font color="#485664"><div style="display:table-cell;white-space:nowrap;vertical-align:top;width:100%"> <span style="padding-right:6px;font-weight:500"><b>From:</b> Pierre-Yves Chibon <a href="mailto:pingou@pingoured.fr" target="_blank"><pingou@pingoured.fr></a><br></span><font color="#485664"><b>Date:</b> May 11, 2020 at 11:49 PM<br><b>To:</b> <a href="mailto:devel-announce@lists.fedoraproject.org" target="_blank">devel-announce@lists.fedoraproject.org</a><br><b>Subject:</b> Retired packages with maintainers<br></font></div> </font></div></div> <div style="color:rgb(144,154,164);margin-left:24px;margin-right:24px"><pre>Good Morning Everyone, A little while ago we have received the request on the infra issue tracker to remove all maintainers of retired packages [1]. So today I decided to look at what this would look like and wrote a script that queries PDC for the list of all branches on all projects [2], gather from it a list of all the packages that are retired on all their branches (so all branches are ``active=false``). For each of these retired project, it queries dist-git to find out if they still have maintainers in addition to the ``orphan`` user. The outcome of this script can be found there: <a href="https://pingou.fedorapeople.org/retired_packages_with_maintainers.log" target="_blank">https://pingou.fedorapeople.org/retired_packages_with_maintainers.log</a> Some stats about this: - 881 RPM packages are retired and still have maintainers (out of 4322 retired RPMs). - 662 of them are not orphaned - 42 modules are retired and still have maintainers (out of 42 retired modules). - all of them are not orphaned - 2 containers are retired and still have maintainers (out of 3 retired containers). - all of them are not orphaned Which brings a couple of questions: - Do we have a documented way to mark modules as orphaned or retired? - Should we orphan all the RPM packages that are retired but not orphaned? Finally, does everyone agree about the original request: "remove all maintainers of retired packages"? Or should we bring this to FESCo? Thanks for your inputs, Pierre [1] <a href="https://pagure.io/fedora-infrastructure/issue/8600" target="_blank">https://pagure.io/fedora-infrastructure/issue/8600</a> [2] <a href="https://pdc.fedoraproject.org/extras/active_branches.json" target="_blank">https://pdc.fedoraproject.org/extras/active_branches.json</a> (8+Mb file) _______________________________________________ devel-announce mailing list -- <a href="mailto:devel-announce@lists.fedoraproject.org" target="_blank">devel-announce@lists.fedoraproject.org</a> To unsubscribe send an email to <a href="mailto:devel-announce-leave@lists.fedoraproject.org" target="_blank">devel-announce-leave@lists.fedoraproject.org</a> Fedora Code of Conduct: <a href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" target="_blank">https://docs.fedoraproject.org/en-US/project/code-of-conduct/</a> List Guidelines: <a href="https://fedoraproject.org/wiki/Mailing_list_guidelines" target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a> List Archives: <a href="https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org" target="_blank">https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org</a> </pre> </div> </blockquote> <br> </div> _______________________________________________<br> SoaS mailing list<br> <a href="mailto:SoaS@lists.sugarlabs.org" target="_blank">SoaS@lists.sugarlabs.org</a><br> <a href="http://lists.sugarlabs.org/listinfo/soas" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/soas</a><br> </blockquote></div>