Looking through the list of sysadmin-qa members, I see some names that might not need to be in there any more. We should probably clean it out. I'm not an admin of that group so I can't, but @kevin can. @tflink can maybe help with this?
Happy to help, just let me know what users to remove... or perhaps we should just make @adamwill an admin to remove them himself?
I actually don't know for sure who should still be in and who should be out; some of the names on the list I don't know and thus don't know why they're in there. We should probably discuss this somewhere Sekrit.
This still seems valid. @tflink , can you help with this?
I don't have clear memories of why everyone was added, either. I think there was a time period where there was an overlap between the sysadmin-qa group and some of the CI stuff but I have no idea if that is still needed.
I wonder if the best way forward wouldn't be to just email the folks that we're not sure about to ask them.
Metadata Update from @kparal: - Assignee reset - Custom field story_points adjusted to 3 - Issue set to the milestone: Undefined Future
One thing we have done in the past is at mention everyone in a ticket (like this one) and give it a week or two and then anyone who didn't chime in that they still want the access can be removed. If someone wants back after a while, they can always be readded.
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/quality/tickets/issues/535
Please continue any further discussion there.