forge/forge
11
8
Fork 8
Code Issues 97 Pull requests 1 Projects Wiki Activity Actions

Organization for the i3 SIG #641

New issue
Closed
opened 2026-07-01 17:46:38 +00:00 by x3mboy · 8 comments
x3mboy commented 2026-07-01 17:46:38 +00:00
Copy link

Eligibility Criteria

  • Infrastructure and Operations: Configuration management, deployment scripts, or tooling used by the Fedora Infrastructure team to run the project.
  • Release Engineering and Packaging: Tools, scripts, and templates used to build, compose, and distribute Fedora releases, editions, and spins.
  • Governance and Team Organization: Trackers, documentation, and collaborative spaces for official Fedora Teams, Special Interest Groups (SIGs), Working Groups, and Fedora Council initiatives.
  • Fedora-Specific Software: Software projects conceptualized and developed primarily to serve the Fedora community (e.g., Fedora Badges, Bodhi, fedora-messaging, etc.).

Desired Organization Name (Short Name)

i3-sig

Full Name of Organization

i3 SIG

Description of Organization’s Purpose

These Projects are under the i3-sig namespace making them likely related to the i3-sig group.

Website URL

https://docs.fedoraproject.org/en-US/i3/

https://pagure.io/design/issue/raw/files/4e6d476766fc496caf46be342b24e4c938dcbb7c539a6e6089182ec5986affdd-Fedora_i3_Logo.png

Fedora Accounts Group for Organization Owners

i3-sig

Other Information

I need to move the docs repositories and host some of the repositories that are on pagure:

### Eligibility Criteria - [ ] **Infrastructure and Operations:** Configuration management, deployment scripts, or tooling used by the Fedora Infrastructure team to run the project. - [ ] **Release Engineering and Packaging:** Tools, scripts, and templates used to build, compose, and distribute Fedora releases, editions, and spins. - [x] **Governance and Team Organization:** Trackers, documentation, and collaborative spaces for official Fedora Teams, Special Interest Groups (SIGs), Working Groups, and Fedora Council initiatives. - [ ] **Fedora-Specific Software:** Software projects conceptualized and developed primarily to serve the Fedora community (e.g., Fedora Badges, Bodhi, fedora-messaging, etc.). ### Desired Organization Name (Short Name) i3-sig ### Full Name of Organization i3 SIG ### Description of Organization’s Purpose These Projects are under the `i3-sig` namespace making them likely related to the i3-sig group. ### Website URL https://docs.fedoraproject.org/en-US/i3/ ### Avatar/Logo https://pagure.io/design/issue/raw/files/4e6d476766fc496caf46be342b24e4c938dcbb7c539a6e6089182ec5986affdd-Fedora_i3_Logo.png ### Fedora Accounts Group for Organization Owners i3-sig ### Other Information I need to move the docs repositories and host some of the repositories that are on pagure: - https://pagure.io/i3-sig/docs - https://pagure.io/i3-sig/Fedora-i3-Spin - https://pagure.io/i3-sig/Fedorai3Spin-WelcomeApp <- Still empty, it's WIP on my local now
👍 1
jflory7 commented 2026-07-01 18:36:28 +00:00
Contributor
Copy link

@x3mboy For the new i3 Spin maintainership, there will likely be two new FAS groups:

  • forge-i3-members: Membership linked to i3-sig, anyone in i3-sig is automatically a member. More flexibility in defining permissions into different teams based on "Member" role as a FAS-linked gateway to gaining some write access to the org.
  • forge-i3-owners: A separate FAS group with manually curated members. Grants auto "Owner" role to all repositories in the Forgejo org. This can be linked to another FAS group if one exists already.

My impression is that forge-i3-owners could be you @x3mboy and @defolos. In the initial migration, I am happy to stay on as a member of i3-sig, but after the Forgejo and Fedora Docs migration, I will likely step back formally as a member of the SIG. Although I will always be a supporter, my i3 roots go deep 😁

Is there anyone else who should be a part of the i3 owners group that comes to mind?

@x3mboy For the new i3 Spin maintainership, there will likely be two new FAS groups: - `forge-i3-members`: Membership linked to `i3-sig`, anyone in `i3-sig` is automatically a member. More flexibility in defining permissions into different teams based on "Member" role as a FAS-linked gateway to gaining some write access to the org. - `forge-i3-owners`: A separate FAS group with manually curated members. Grants auto "Owner" role to all repositories in the Forgejo org. This can be linked to another FAS group if one exists already. My impression is that `forge-i3-owners` could be you @x3mboy and @defolos. In the initial migration, I am happy to stay on as a member of `i3-sig`, but after the Forgejo and Fedora Docs migration, I will likely step back formally as a member of the SIG. Although I will always be a supporter, my i3 roots go deep 😁 Is there anyone else who should be a part of the i3 owners group that comes to mind?
x3mboy commented 2026-07-01 18:40:48 +00:00
Author
Copy link

Is there anyone else who should be a part of the i3 owners group that comes to mind?

I think that it is

> Is there anyone else who should be a part of the i3 owners group that comes to mind? I think that it is
👍 1
jflory7 commented 2026-07-01 18:59:31 +00:00
Contributor
Copy link

@x3mboy Also, what do you think about simply having forge.fp.o/i3?

@x3mboy Also, what do you think about simply having `forge.fp.o/i3`?
👍 1
x3mboy commented 2026-07-01 19:13:10 +00:00
Author
Copy link

That works for me

That works for me
👍 1
x3mboy commented 2026-07-13 15:29:49 +00:00
Author
Copy link

This should be probably an infra ticket?

This should be probably an infra ticket?
pbokoc commented 2026-07-13 17:23:14 +00:00
Member
Copy link

@x3mboy wrote in #641 (comment):

This should be probably an infra ticket?

Nah, org requests usually go here.

@x3mboy wrote in https://forge.fedoraproject.org/forge/forge/issues/641#issuecomment-1061679: > This should be probably an infra ticket? Nah, org requests usually go here.
👍 2
jflory7 commented 2026-07-14 14:41:42 +00:00
Contributor
Copy link

@ryanlerch @lenkaseg @t0xic0der This ticket is for one of the last-remaining Fedora Docs repos on Pagure.io, among other repos. Any chance we can prioritize this so we have enough time to work through Pagure migration hiccups, if any?

@ryanlerch @lenkaseg @t0xic0der This ticket is for one of the last-remaining Fedora Docs repos on Pagure.io, among other repos. Any chance we can prioritize this so we have enough time to work through Pagure migration hiccups, if any?
ryanlerch added this to the Sprint 25 project 2026-07-20 01:15:04 +00:00
ryanlerch commented 2026-07-21 03:02:57 +00:00
Owner
Copy link

The i3 organization has been created on Forge.

We have created the forge-i3-owners group in Fedora Accounts, with @defolos and @x3mboy added as sponsors and members.

We have also created the forge-i3-members group in Fedora Accounts. This group has no sponsor, but its membership is inherited from the i3-sig Fedora Accounts group.

The group-team mappings have been configured so that members of forge-i3-owners will be added to the Owners team, and members of forge-i3-members will be added to the Members team in the i3 organization on Forge.

Please note that users will need to log out and log back in to Forge for the team mappings to take effect.

The [`i3`](https://forge.fedoraproject.org/i3) organization has been created on Forge. We have created the [`forge-i3-owners`](https://accounts.fedoraproject.org/group/forge-i3-owners/) group in Fedora Accounts, with @defolos and @x3mboy added as sponsors and members. We have also created the [`forge-i3-members`](https://accounts.fedoraproject.org/group/forge-i3-members/) group in Fedora Accounts. This group has no sponsor, but its membership is inherited from the [`i3-sig`](https://accounts.fedoraproject.org/group/i3-sig/) Fedora Accounts group. The group-team mappings have been configured so that members of `forge-i3-owners` will be added to the `Owners` team, and members of `forge-i3-members` will be added to the `Members` team in the `i3` organization on Forge. Please note that users will need to **log out and log back in** to Forge for the team mappings to take effect.
🚀 1
ryanlerch 2026-07-21 03:03:35 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
docs
No results found.
Labels
Clear labels   
ai-review-please
label for requesting AI code review

  
Org/Team Modification

   
Private Issues
Label for tracking development on Private Issues in Forgejo

  
Runner Request
  
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
 Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
 Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
 Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
 Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
 User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
ai-review-please
Org/Team Modification
Private Issues
Runner Request
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 25
Assignees
Clear assignees
No assignees
ryanlerch
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forge/forge#641
No description provided.