Describe what you would like us to do:

@ryanlerch Where did we document the gitlab permissions conventions?

basically we need to make fas groups for each permission level in gitlab (owner, developer, etc).

I think we'd want the go-sig group to have developer access by default and then a go-sig-gitlab-owners group to manage the owner role, unless it's possible to manage the owner role directly in Gitlab without a second FAS group. I prefer having -gitlab- in there to make it clear that this is about Gitlab ACLs and not some separate "exclusive" part of the Go SIG.

we can use any groups you want here, but typically in the past, the convention is:

go-sig maps to developers on gitlab
go-sig-admin maps to owner on gitlab

cant remember where we formally documented this, but this thread outlines it:

https://discussion.fedoraproject.org/t/fedora-docs-gitlab-permissions/39545

That said, we can map any group you want to any role, but tpyically in the past groups have only wanted developer and owner roles, and we have just used the -admin suffix when making the new group

I'd prefer to map go-sig to the developerrole and create a new go-sig-gitlab-owners group for the owner role if possible. If not, go-sig-admin works.

So, thats not the convention I recall... but I can't find the discussion off hand either.

My recollection was:

gitlab-fedora-$group-$role

so,

gitlab-fedora-go-sig-admin
gitlab-fedora-go-sig-developers

But I also see the value in just mapping the existing group to developers.
(The fedora is in there because centos uses our same ipa cluster).

So, how about:

go-sig map to developer
and
gitlab-fedora-go-sig-admin map to owner?

Also, do note that with this mapping gitlab will remove anyone manually added. it syncs that group and will remove anyone added/removed/changed permission levels. :)

So, how about:

go-sig map to developer
and
gitlab-fedora-go-sig-admin map to owner?

Works for me!

Any updates here? We would really like to move forward with this.

sorry about the slow response!

so https://gitlab.com/fedora/sigs/go is now ready to go.

anyone in the go-sig group will have "Developer" access when logging in with Fedora SAML.

i also made the go-sig-admin group have "Owner" access. there is currently noone in thatr group, but i gave @ignatenkobrain and @ngompa sponsor privs on there.

if we could get a list of who should be sponsors of these two groups, that would be awesome (also @gotmax23 i noticed you arent a sponsor of go-sig, so i probably should have an ok from a sponsor before adding you to either of these groups. )

Thanks for creating the namespace! I think we want @alexsaezm and @gotmax23 as sponsors of both groups. I'm planning to lead the Gitlab transition and am otherwise very active, and @alexsaezm is our (informal) chair and the main golang maintainer. @ignatenkobrain is no longer active in the Go SIG, but I can ask @ngompa.

I'm still active, though I'm not a fan of GitLab, I intend to still participate.

All done, sorry for the delay here.