On Tue, Aug 20, 2024 at 2:33 PM Richard Megginson rmeggins@redhat.com wrote:
On Tue, Aug 20, 2024 at 12:17 PM Neal Gompa ngompa13@gmail.com wrote:
On Tue, Aug 20, 2024 at 11:51 AM Richard Megginson rmeggins@redhat.com wrote:
On Tue, Aug 20, 2024 at 3:02 AM Emmanuel Seyman emmanuel@seyman.fr wrote:
I finally got to Flock on Wednesday afternoon, shortly after 2pm. Since the afternoon sessions had already started, I sat down on one of them ("Git forge replacement" by Tomáš Hrčka). Once the afternoon sessions were done, I was able to say hi to a few other attendees before going to my room and getting settled in.
On Thursday, I met Maxwell G and talked about the packaging guidelines for Ansible collections[1] he had written. Because I didn't know these guidelines existed, I need to check that my source-rpm of the robertdebock roles conform to them before submitting it to Fedora for review.
I then had the opportunity to talk to Neal Gompa about the linux-system-roles package, which contains a number of roles that are important to the Fedora Server SIG. Neal explained that he only owned the package because it had been orphaned and that he did not want to see it be retired. He told me he would much prefer a member of the SIG be one of the packagers so we ended up giving me the commit bit on the packager.
I'm not sure what you mean by "owner" in this context. Is that strictly the Bugzilla assignee of the package? Looking at https://src.fedoraproject.org/rpms/linux-system-roles - I see that ngompa is the Bugzilla assignee for Fedora and EPEL. spetrosi and I are the primary maintainers. And the maintenance is done almost entirely by packit automation - the upstream repo uses https://github.com/linux-system-roles/auto-maintenance/blob/main/.packit.yam...
Packit automation is no excuse to ignore when a package gets orphaned and potentially retired. I took it because it became obvious nobody noticed it was about to be retired and it's core to Fedora Server.
Understood. So how do I ensure that the linux-system-roles package doesn't get flagged as potentially orphaned in the future? Should I use my account to make periodic pagure merge requests?
It got orphaned presumably because the original primary maintainer was inactive for so long that their packager rights were automatically removed and all their packages were orphaned: https://pagure.io/fedora-infrastructure/issue/11901
Making sure you have activity ensures that doesn't happen.