Fedora Forge Update

Project Discussion
, , ,
3

Thank you for your questions about the differences between Organizations and Teams in Forgejo! This is indeed a common source of confusion, especially when migrating from Pagure.io. Let me break this down clearly.

What’s the difference between an Organization and a Team?

Organizations are the top-level containers that group related repositories together - they represent the “namespace” or “group” concept from Pagure.io. Organizations themselves don’t have permissions - they’re just containers. Examples would be rust-sig, infrastructure, or council.

Teams are permission groups within an Organization that define who can do what. They control access to repositories within an Organization and have specific permission levels (Read, Write, Admin, Owner). Examples would be owners, contributors, or members.

Think of it this way: Organization = The “SIG” or “team” or “subproject”, and Team = The “roles” within that SIG/team/subproject.

You need both because Organizations provide the namespace structure (like Pagure.io namespaces) while Teams provide the permission management (like Pagure.io group permissions).

For your Rust SIG migration:

Based on your description, here’s how the migration would work:

Current Pagure.io Setup:

  • FAS Group: rust-sig

  • Pagure Group: fedora-rust

  • Pagure Namespace: fedora-rust/*

  • Permissions: fedora-rust group has admin access to most projects

Recommended Forgejo Setup:

  • Organization: rust-sig

  • Team 1: owners – maps to a new FAS group forge-rust-sig-owners with Owner permissions (the forge-- convention is something we are using for new FAS groups we make, but we can by all means reuse existing FAS groups)

  • Team 2: members – maps to FAS group rust-sig with Write permissions

  • Repositories: All migrated fedora-rust/* projects under rust-sig organization

Important Notes:

  • Team membership on Fedora Forge is managed exclusively through FAS groups. You cannot add or remove team members directly through the Forgejo UI - all membership changes must be made in the corresponding FAS group.

  • We typically are aiming to avoid using the fedora- prefix for organization names since all organizations on Fedora Forge are Fedora-related, making the prefix redundant.

8 Likes