#9117 Add oamg group to the list of src.fedoraproject.org access groups
Closed: Fixed 3 years ago by pingou. Opened 3 years ago by mbocek.

I'd like to make the oamg FAS group an admin of the convert2rhel package repo. When I go to https://src.fedoraproject.org/rpms/convert2rhel/addgroup, the group is not available there. By looking at the other groups available, all of them seem to be of the pkgdb type. I've changed the type of the oamg group to pkgdb three days ago yet it's still not being listed on the page where I can assign the admin rights for a package.

Screenshot_from_2020-07-07_10-41-27.png


This expected, changing the group type does not create the group on dist-git.

There are a number of requirements and recommendations for groups to be created on dist-git.

I have tried to document them in https://pagure.io/fedora-infra/howtos/blob/master/f/groups_in_fedora.md

So if you would like a group to be created in dist-git, we strongly recommend it follows the *-sig pattern. It should be linked to a bugzilla account via its mailing list field (so since this is a group, most often it is recommended that private mailing list be created for this purpose).
And finally, since this is a packager group, it must require people to be in the packager group as a prerequisite (unlike oamg which currently only require the FPCA to be signed).

Thanks a lot, @pingou . I was googling for such a document with no luck.

Our team uses a private mailing list leapp-notifications@redhat.com which is associated with a bugzilla account (e.g. this bug is assigned to it). I've set this mailing list to the oamg FAS account.

Would it be enough if I rename the group from oamg to oamg-sig, instead of creating a new group?

I don't think we can rename groups :(

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, medium-gain, medium-trouble, src.fp.o

3 years ago

Ah, I see. I can change just group description. I'll create a new group then.

Do you have the permissions to create the group? Otherwise I can create it for you.

Does oamg-sig work for you as group name, or would you prefer leapp-sig or something else?

Frankly I don't remember how did I create the oamg group back then. So please, create it for me.

Since we'd use this group for the convert2rhel only (the OAMG team takes care of couple more packages but those are in RHEL only), you can name it convert2rhel-sig.

And, if you have a guide how to make FAS users part of the packager group handy, I could tell guys who should be in the group to go through that.

Thank you.

Frankly I don't remember how did I create the oamg group back then. So please, create it for me.
Since we'd use this group for the convert2rhel only (the OAMG team takes care of couple more packages but those are in RHEL only), you can name it convert2rhel-sig.

No problem, on it

And, if you have a guide how to make FAS users part of the packager group handy, I could tell guys who should be in the group to go through that.

Well it will be the usuals: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers and https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group

The group has been created: https://admin.fedoraproject.org/accounts/group/view/convert2rhel-sig please set up the mailing list and I'll create the group in dist-git :)

Thanks, mailing list added. You can create the group in dist-git. My colleagues will go through the process for becoming fedora maintainers in the meantime.

# pagure-admin new-group convert2rhel-sig  mbocek --display="convert2rhel-sig"
Using configuration file `/etc/pagure/pagure.cfg`
Group management has been turned off for this pagure instance
Do you want to continue? [y/N]y
Group `convert2rhel-sig` created.
User `mbocek` added to the group `convert2rhel-sig`.

The group has been created. Groups membership from FAS are synced upon login, so new members will need to log out from src.fedoraproject.org and back in to their membership updated.

Let us know if you need anything else :)

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Thanks a lot, Pierre.

Login to comment on this ticket.

Metadata
Attachments 1