Initially I thought I'm going to ask for ruby-sig PkgDB group, but now I discovered #5478 and https://pagure.io/fedora-commops/issue/84. So to keep things consistent (this should really be documented somewhere), could you create:
group: ruby-sig This will allow to track Ruby SIG members.
group: ruby-packagers-sig This will be used to provide group access to the ruby packages.
Strangely enough, I was thinking of proposing the 'ruby-packagers' group to you yesterday :). These group names look great IMHO.
Thank you for thorough investigation!
ok. I've created the 'ruby-sig' group. It's just a normal fas tracking group with you as admin.
For the ruby-packagers-sig we need to make a mailing list that is private (since it will get all bugzilla info, including security issues). Shall I just make a 'ruby-packagers-sig' list for that?
Thx
Yep, sounds good to me.
ok. I have created the ruby-packagers-sig FAS group and the ruby-packagers-sig mailing list.
You now need to create a bugzilla account for the group. Just go to bugzilla.redhat.com, make a new account with address ruby-packagers-sig@lists.fedoraproject.org and then go to https://lists.fedoraproject.org/admin/lists/ruby-packagers-sig.lists.fedoraproject.org/held_messages to find the initial settings message, ack it and set whatever secure password you like for the account.
You can then subscribe it to the list to allow it's postings through and then in pkgdb you can add it to whatever ruby packages you like.
Let us know if you run into any problems... :gem:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thank you.
Actually I have additional questions about best practices. Is it better to transfer the ownership of the package to the group or just add the group as an administrator? Should be the group preferably the only administrator/committer of the package?
Groups can be made PoC but cannot have approveacls, so you can put it as commiter but you won't be able to make it an admin.
But once the group is PoC, any member of the group can add admins, right? If the previous assumption right, isn't then the admin restriction a bit paranoid? Is it by design or is it some technical limitation?
But once the group is PoC, any member of the group can add admins, right?
Nope, being PoC does not give you anything but the privilege to be assigned to bug reports on bugzilla :)
You could be PoC and not have commit for example, or no approveacls (which would be the case for groups). The tooling in pkgdb gives you everything when you adopt or give a package but it's purely enforced by the tooling.
Login to comment on this ticket.