forge/forge
10
7
Fork 5
Code Issues 87 Pull requests 1 Projects 3 Wiki Activity Actions

New organisation for Fedora Code of Conduct committee + migration #385

New issue
Closed
opened 2026-02-06 14:15:12 +00:00 by ankursinha · 6 comments
ankursinha commented 2026-02-06 14:15:12 +00:00
Copy link

Hello,

Could we please have a new organization for the Fedora Code of Conduct committee (and migrate its repos)?

Note: the CoC requires private issues that are visible only to the CoC organisation members, so this needs to be tested + verified before the migration is done.

Hello, Could we please have a new organization for the Fedora Code of Conduct committee (and migrate its repos)? - Desired organisation name (Short name): CoC - Full name of the organisation: Fedora Code of Conduct Commitee - Description: The Fedora Code of Conduct Committee is the body responsible for maintaining the CoC and its enforcement in the community. - Website URL: https://docs.fedoraproject.org/en-US/project/code-of-conduct/committee/ - Avatar/Logo: N/A - Fedora accounts group for organisation owners/admins: coc-owners - Fedora accounts group for organisation members: coc-members - Repositories entailed: https://pagure.io/CoC - Upstream ticket: https://pagure.io/CoC/issue/368 (currently private) **Note**: the CoC requires private issues that are visible only to the CoC organisation members, so this needs to be tested + verified before the migration is done.
jflory7 commented 2026-02-06 14:27:15 +00:00
Contributor
Copy link

I approve! 👍

I approve! 👍
t0xic0der added this to the Backlog project 2026-02-09 09:18:02 +00:00
ryanlerch modified the project from Backlog to Sprint 14 2026-02-09 11:04:55 +00:00
t0xic0der modified the project from Sprint 14 to Backlog 2026-02-23 10:27:04 +00:00
t0xic0der modified the project from Backlog to Sprint 15 2026-02-23 10:33:29 +00:00
t0xic0der commented 2026-02-26 04:27:20 +00:00
Member
Copy link

The namespace and the associated teams (for owners and members) have been created.

Since private issue tickets on a public repository are not a thing yet on Forgejo, do you want to proceed here using private repositories (as issue tickets opened in a private repository default to the private visibility) or do you want to wait until the private issue tickets are implemented (which will take quite a while and we do not want to keep Pagure around for that long)? Also, you do not seem to have mentioned whom we should add to the aforementioned groups. Do you want us to create empty groups with @jflory7 and @ankursinha as sponsors so that you can add them? Please help us with this information, and we can proceed further.

The [namespace](https://forge.fedoraproject.org/CoC) and the associated [teams](https://forge.fedoraproject.org/org/CoC/teams) (for [owners](https://forge.fedoraproject.org/org/CoC/teams/owners) and [members](https://forge.fedoraproject.org/org/CoC/teams/members)) have been created. Since private issue tickets on a public repository are not a thing yet on Forgejo, do you want to proceed here using private repositories (as issue tickets opened in a private repository default to the private visibility) or do you want to wait until the private issue tickets are implemented (which will take quite a while and we do not want to keep Pagure around for that long)? Also, you do not seem to have mentioned whom we should add to the aforementioned groups. Do you want us to create empty groups with @jflory7 and @ankursinha as sponsors so that you can add them? Please help us with this information, and we can proceed further.
jflory7 commented 2026-02-26 05:07:06 +00:00
Contributor
Copy link

@t0xic0der We don't have a FAS group for the Code of Conduct Committee, so we will need to make one. If we can make the FAS group as a part of this ticket, it should have all current members of the FAS group as members. For now, just me, Jona, and Jef should be sponsors.

Please add the following members to the FAS group: @jflory7 @jspaleta @jonatoni @chris @ankursinha @dcantrell

Similar to the GDPR data deletion repo, the Fedora Code of Conduct requires a publicly-accessible ticket tracker with private issues. This is a non-negotiable feature for our legal requirements for this project process. An email workflow without tickets is not viable for how we achieve legal compliance and risk mitigation.

The purpose of this ticket is to give us a chance of testing the new Forgejo tools and building a space ahead of private issues being implemented, so we can be ready when the time comes.

@t0xic0der We don't have a FAS group for the Code of Conduct Committee, so we will need to make one. If we can make the FAS group as a part of this ticket, it should have all current members of the FAS group as members. For now, just me, Jona, and Jef should be sponsors. Please add the following members to the FAS group: @jflory7 @jspaleta @jonatoni @chris @ankursinha @dcantrell Similar to the GDPR data deletion repo, the Fedora Code of Conduct requires a publicly-accessible ticket tracker with private issues. This is a non-negotiable feature for our legal requirements for this project process. An email workflow without tickets is not viable for how we achieve legal compliance and risk mitigation. The purpose of this ticket is to give us a chance of testing the new Forgejo tools and building a space ahead of private issues being implemented, so we can be ready when the time comes.
t0xic0der commented 2026-02-27 04:18:00 +00:00
Member
Copy link

@ryanlerch, could you please create a forge-coc-owners FAS group with @jflory7, @jonatoni and @jspaleta as both sponsors and members and a forge-coc-members FAS group with the aforementioned three as sponsors but @ankursinha, @chris, @dcantrell, @jflory7, @jonatoni and @jspaleta as members? I have also opened a pull request to perform the team and group mappings.

@ryanlerch, could you please create a `forge-coc-owners` FAS group with @jflory7, @jonatoni and @jspaleta as both sponsors and members and a `forge-coc-members` FAS group with the aforementioned three as sponsors but @ankursinha, @chris, @dcantrell, @jflory7, @jonatoni and @jspaleta as members? I have also opened a [pull request](https://forge.fedoraproject.org/infra/ansible/pulls/3180) to perform the team and group mappings.
👍 1
ryanlerch commented 2026-03-02 03:40:00 +00:00
Owner
Copy link

Done:

Done: * https://accounts.fedoraproject.org/group/forge-coc-members/ * https://accounts.fedoraproject.org/group/forge-coc-owners/
t0xic0der commented 2026-03-02 05:17:30 +00:00
Member
Copy link

The pull request has been merged.

@ankursinha, @chris, @dcantrell, @jflory7, @jonatoni and @jspaleta, please log out and log back in to let the updated mapping take effect. From there on out, you should be able to take the namespace for a spin. Please feel free to reopen this ticket should you face issues.

The [pull request](https://forge.fedoraproject.org/infra/ansible/pulls/3180#issuecomment-561832) has been merged. @ankursinha, @chris, @dcantrell, @jflory7, @jonatoni and @jspaleta, please log out and log back in to let the updated mapping take effect. From there on out, you should be able to take the namespace for a spin. Please feel free to reopen this ticket should you face issues.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
docs
No results found.
Labels
Clear labels   
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 could be worked on immediately when capacity is available.

  
Chore

Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
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.

  
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
Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
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
This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
Sprint Status
Review
This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
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 improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

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

  
Work Item
Epic

  
Work Item
Spike

  
Work Item
Task

  
Work Item
User Story

  
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
Backlog Status
Needs Review
Backlog Status
Ready
Chore
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
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 15
Assignees
Clear assignees
No assignees
ryanlerch
t0xic0der
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#385
No description provided.