#12888 [Forgejo] New Organization and Teams Request: Cloud SIG
Closed: Fixed a month ago by ryanlerch. Opened a month ago by jcline.

Hello Fedora Infra Team,

I would like to request the creation of a new organization and associated
teams in Fedora Forge.

  1. New Organization Details:

Desired Organization Name (Short Name): cloud

Full Name of Organization: Fedora Cloud Special Interest Group

Description of Organization's Purpose: This organization will host repositories
and manage collaboration for the Cloud SIG, focusing on developing and
maintaining Cloud images and tooling. In particular, it'll include a ticket tracker to replace https://pagure.io/cloud-sig/issues as well as tools like https://pagure.io/cloud-image-uploader/.

Website URL (Optional): https://docs.fedoraproject.org/en-US/cloud/

Avatar/Logo (Optional): No avatar at this time

Fedora Accounts Group for Organization Owners: forge-cloud-owners

  1. New Team Details (within 'cloud' organization):

Team 1:

Target Organization Name: cloud

Team Name: members

Description of Team's Purpose: Core team responsible for code contributions and
repository management.

Desired Permission Level in Forgejo: Write

Fedora Accounts Group to Map to Team: forge-cloud-members

Include all repositories?: Yes

Please let me know if any further information is required.

Note: There's an existing cloud-sig group (https://accounts.fedoraproject.org/group/cloud-sig/) but it sounds like from the documentation that new groups must be created (forge-cloud-owners, fedora-cloud-members). These two groups don't exist yet, but I hope it's okay to have that as part of this request? The sponsors and members of the current cloud-sig could be mapped to owners and members respectively.

Thank you,
jcline


We should probably map to the cloud-sig instead, and merge all the the different things into that namespace.

There's also pagure.io/fedora-cloud to pull in.

Fedora Accounts Group to Map to Team: forge-cloud-members

We shouldn't have two separate groups for this. It makes more sense to just reuse cloud-sig and fix the membership there.

Fedora Accounts Group to Map to Team: forge-cloud-members

We shouldn't have two separate groups for this. It makes more sense to just reuse cloud-sig and fix the membership there.

I just followed the form on https://docs.fedoraproject.org/en-US/forge-documentation/requesting_new_org_or_team/ and it sounds like that's the expected pattern. Cloud isn't a special snowflake so I guess it should just do whatever everything else is doing (whether that's one group or two).

Now I wonder what we should be doing here...

Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: forgejo_migration, low-trouble, medium-gain, ops

a month ago

Metadata Update from @ryanlerch:
- Issue assigned to ryanlerch

a month ago

Thanks for using Fedora Forge!

I have:

  1. Created the forge-cloud-owners Fedora Accounts group with the following:
  2. Created the forge-cloud-members group with the following:
  3. Created the new cloud organization on Fedora Forge -- https://forge.fedoraproject.org/cloud/
  4. Added 2 teams to the new cloud org:
  5. Updated the teams mapping so the Fedora Accounts teams map, and on next login any users in the Fedora Accounts groups will be granted access to the mapped teams in Fedora Forge.
  6. Changed the avatar to the fedora logo.

Next Steps
1. Update the settings for your org, including the details like description etc -- https://forge.fedoraproject.org/org/cloud/settings
2. File a request for an icon with the design team to use as your avatar here on forge: https://gitlab.com/fedora/design/team/requests/-/issues
3. Add a profile page for your organization: https://docs.fedoraproject.org/en-US/forge-documentation/create_org_profile_page/
4. Migrate from Pagure: https://docs.fedoraproject.org/en-US/forge-documentation/migration/pagure_repository/

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

a month ago

Log in to comment on this ticket.

Metadata