Hello Fedora Infra Team,
I would like to request the creation of a new organization and associated teams in Fedora Forge.
Desired Organization Name (Short Name): commops Full Name of Organization: Community Operations Description of Organization's Purpose: This organization will host repositories and coordinate collaboration for the Fedora CommOps team, focusing on contributor experience, community metrics, and engagement support. Website URL (Optional): https://docs.fedoraproject.org/en-US/commops/ Avatar/Logo (Optional): https://gitlab.com/uploads/-/system/group/avatar/78322641/Community_Operations_logo_-_icon_blue_square.png Fedora Accounts Group for Organization Owners: sponsors of "commops"
Team 1: Target Organization Name: commops Team Name: commops-members Description of Team's Purpose: CommOps Members, contributors participating in projects, metrics, and community operations. Desired Permission Level in Forgejo: Write Fedora Accounts Group to Map to Team: members of commops Include all repositories?: Yes
Please let me know if further information is required.
Thank you, Robert Wright (fas: rwright)
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble
Friendly ping. Is this doable? I see other groups are getting added to Forge, but I wanted to know if there is an ETA I can share to the rest of CommOps on this. :)
@humaton Could you look into this?
Metadata Update from @humaton: - Issue assigned to humaton - Issue tagged with: forgejo_migration
The missing commops-members group was created in IPA. The organization was created in the new forge, and mappings were updated. It might take a few hours, but you should become an owner of the new org @rwright
Hey there!
Thanks - maybe I should clarify and maybe make sure I made the request right. My intent of "commops-members" was members of the FAS group commops (I was trying my best to map from teh Fedora Discussion guide to make this request and I might have misundersood :smile: ).
Do we need an extra FAS group or can we just use the existing commops group?
You need 2 teams in the forge. One team, called Owners, is the people who have admin access to the whole organization and all repositories. And the Members team that can have granular access or rw to all repos.
I mapped the commops group from FAS to the Owners team and created a new FAS group called commops-members that is mapped to the Organization team Members.
Now rereading your request, you probably want me to create the commops-owners group in FAS and do the mapping the other way around. Did I get it right?
Yes, I think so. I was hoping we could just use whoever was a sponsor of the existing CommOps group as an owner, but if we need a separate group, that's fine. Thank you and again, my apologies for the confusion!!
So there are 2 fas groups commops that is mapped to Members group in the new forge. And a new group commops-owners members are @rwright and @jflory7.
Hey there - I checked on login and I am just a member of the group. It doesn't seem like permissions sync'd.
@rwright
Okay, we are preferring to use the new "forge-*" groups to avoid confusion -- except in super well-defined places like council -- and then we are using those very sparingly.
council
I have set up the following structure for you, and added it to the groups mappings:
Users will need to log out and log back in if they dont have their permissions.
Group: https://accounts.fedoraproject.org/group/forge-commops-owners/ is mapped to the Owners team on Fedora Forge. Members of that fas group will be assigned to that Fedora Forge team when they next login. On this FAS Group There are 2 owners (rwright,jflory7) and 2 members (rwright, jflory7)
Group: https://accounts.fedoraproject.org/group/forge-commops-members/ is mapped to the Owners team on Fedora Forge. Members of that fas group will be assigned to that Fedora Forge team when they next login. On this FAS Group There are 2 owners (rwright,jflory7) and 17 members (all the members of the existing commops group have been added there)
there were no group mappings set up either -- so i have done that.
Metadata Update from @ryanlerch: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)