Requesting a New Organization and/or Team in Fedora Forge
DRAFT DOCUMENTATION: This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies. |
Purpose
This document outlines the standardized process for Fedora Project contributors
to formally request the creation of a new organization within Fedora Forge, or
the addition of new teams to an existing organization. By following this
procedure, users can ensure their requests are complete, contain all necessary
configuration details, and can be processed efficiently by the fedora-infra
team.
Scope
This Standard Operating Procedure (SOP) applies to all Fedora Project contributors who require a new organization for their project, Special Interest Group (SIG), or working group, or who need to establish new teams within an existing Fedora Forge organization to manage permissions and user access.
Prerequisites
Before submitting a request, please ensure you have the following information ready:
-
Clear Justification: A clear understanding of why a new organization or team is needed.
-
Existing Fedora Accounts Group(s): Identify the specific Fedora Accounts group(s) whose members will be mapped to the
Owners
team of a new organization, and/or to any new teams you are requesting. Ensure these Fedora Accounts groups exist and contain the correct members. -
All Required Details: Gather all the specific information outlined in the "Procedure" section below for your request type (new organization, new team, or both).
Procedure: Filing a Request Ticket
All requests for new organizations and/or teams in Fedora Forge must be
submitted by filing a ticket in the fedora-infra
ticket tracker.
When creating your ticket, provide all the relevant details as specified below. The more complete and accurate your request, the faster it can be processed.
1. New Organization Request Details
If you are requesting a new organization, include the following information in your ticket:
Desired Organization Name (Short Name)
This will be the short URL component for your organization (e.g., forge.fedoraproject.org/org/myawesomesig
). It should be unique, lowercase, and typically hyphen-separated.
myawesomesig
Full Name of Organization
This is the human-readable, full name of your organization that will appear in the UI.
My Awesome Special Interest Group
Description of Organization’s Purpose
A brief description of your organization’s purpose or mission.
This organization will host repositories and manage collaboration
for the My Awesome SIG, focusing on [briefly describe focus].
Avatar/Logo (Optional)
An optional link to an image file for your organization’s avatar/logo. You can also state that you will provide one later.
Fedora Accounts Group for Organization Owners
Specify the existing Fedora Accounts group whose members will automatically become the Owners
of this new organization. The "Owners" team is a special, immutable team with full administrative control over the organization.
forge-myawesomesig-owners
This Fedora Accounts group must already exist. |
2. New Team Request Details (For New or Existing Organizations)
If you are requesting new teams (either within a new organization you’re requesting, or an existing one), include the following information for each team:
-
Target Organization Name:
myawesomesig
(if part of a new org request) or
existing-fedora-org
(if adding to an existing org).
-
Team Name:
members
-
Description of Team’s Purpose (Optional):
Team for core developers working on the main project
repositories.
-
Desired Permission Level in Forgejo:
Choose one of: Read
, Write
, Admin
.
|
-
Fedora Accounts Group to Map to Team:
This is critical. Specify the existing Fedora Accounts group whose members will automatically be added to this new team in Forgejo.
forge-myawesomesig-members
(ensure this Fedora Accounts group already exists).
-
Include all repositories? (Yes/No):
Indicate if this team should have the specified permission level on all current and future repositories within the organization.
If your organization contains private repositories, selecting "Yes" will grant the chosen permission level to all private repositories within the organization as well. Ensure this aligns with your security requirements. If "No," you will need to manually request repository assignments later (or specify them in the ticket if known). |
Example Request Ticket Content
You can copy and paste the following template into your fedora-infra
ticket,
filling in the bracketed information.
Subject: [Forgejo] New Organization and Teams Request: My Awesome SIG
Body:
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): myawesomesig
Full Name of Organization: My Awesome Special Interest Group
Description of Organization's Purpose: This organization will host repositories
and manage collaboration for the My Awesome SIG, focusing on developing and
maintaining [specific software/project].
Website URL (Optional): https://fedoraproject.org/wiki/My_Awesome_SIG
Avatar/Logo (Optional): (Will provide a link to an image file later / No avatar
at this time)
Fedora Accounts Group for Organization Owners: forge-myawesomesig-owners
2. New Team Details (within 'myawesomesig' organization):
Team 1:
Target Organization Name: myawesomesig
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-myawesomesig-members
Include all repositories?: Yes (This team should have write access to all
current and future repositories in 'myawesomesig'.)
Please let me know if any further information is required.
Thank you,
[Your Name/Fedora Account]
Want to help? Learn how to contribute to Fedora Docs ›