forge/forge
9
0
Fork 1
Code Issues 58 Pull requests Projects 3 Wiki Activity Actions

Create new organisation and team on Fedora Forge for Fedora Design #313

New issue
Open
opened 2025-12-02 09:50:40 +00:00 by t0xic0der · 4 comments
t0xic0der commented 2025-12-02 09:50:40 +00:00
Member
Copy link

Create new organisation and team on Fedora Forge for Fedora Design

As the Fedora Design team has elected to proceed with the floating migration route, let us go ahead with the creation of the namespace for them and begin migrating the repositories from GitLab.

Create new organisation and team on Fedora Forge for Fedora Design As the Fedora Design team has elected to proceed with the floating migration route, let us go ahead with the creation of the namespace for them and begin migrating the repositories from GitLab. - Desired organisation name (Short name): `designteam` (taken from https://accounts.fedoraproject.org/group/designteam/) - Full name of the organisation: Fedora Design Team - Description of organisation's purpose: Fedora Design team is a Fedora Project's in-house design agency for providing artwork designs, user experience, usability evaluation and design services to the Fedora Project community. - Website URL: https://docs.fedoraproject.org/en-US/design/ - Avatar/Logo: https://gitlab.com/uploads/-/system/group/avatar/14453785/Screenshot_from_2022-12-09_18-45-06.png?width=48 - Fedora accounts group for organisation owners: `designteam-admin` (taken from https://accounts.fedoraproject.org/group/designteam-admin/) - Repositories entailed: All repositories under the Fedora Design namespace (i.e. https://gitlab.com/fedora/design/team) are to be moved over
t0xic0der commented 2025-12-02 09:52:42 +00:00
Author
Member
Copy link

@ekidney I have created the ticket with preliminary information, please provide more information as and when needed to help us migrate the repositories over. Thanks in advance!

@ekidney I have created the ticket with preliminary information, please provide more information as and when needed to help us migrate the repositories over. Thanks in advance!
ryanlerch commented 2025-12-02 11:36:31 +00:00
Owner
Copy link

a couple questions:

  1. is designteam-admin used for anything else? all groups are following the forge-<orgname>-<teamname> setup we have defined in: https://docs.fedoraproject.org/en-US/forge-documentation/fas_group_naming_standards/ we have ways to use existing groups with inhertiance, but if this is the only use for the FAS group, it is better to just make a new group TBH.
  2. is design suitable here for an organization name? all the other orgs have been encouraged to drop the fedora prefix and other suffixes like -sig so team is in this category IMHO.
  3. What other forge teams are needed for this org? Most other orgs have a members team, but it can be anything the design team wants, and however many they want
a couple questions: 1. is `designteam-admin` used for anything else? all groups are following the `forge-<orgname>-<teamname>` setup we have defined in: https://docs.fedoraproject.org/en-US/forge-documentation/fas_group_naming_standards/ we have ways to use existing groups with inhertiance, but if this is the only use for the FAS group, it is better to just make a new group TBH. 2. is `design` suitable here for an organization name? all the other orgs have been encouraged to drop the `fedora` prefix and other suffixes like `-sig` so `team` is in this category IMHO. 3. What other forge teams are needed for this org? Most other orgs have a `members` team, but it can be anything the design team wants, and however many they want
jflory7 commented 2025-12-08 15:31:08 +00:00
Copy link

Discussed in 2025-12-08 Design Team meeting.

The Design Team uses GitLab as our forge of choice at the moment. We discussed this in our meeting, and had a few questions of our own:

  1. For GitLab migrations, is it possible to migrate issues to Forgejo, including the sequence of issue numbers? Will we need to change our numbering system?
  2. Is there any support for GitLab Epics? The Design Team heavily uses epics in GitLab and it would help to know whether these will migrate over somehow, or if we have to leave them behind.
  3. Will design assets, like image uploads and files, will those move from GitLab to Forgejo?

Here is some of my perspective to Ryan's clarifying questions:

  1. I think designteam-admin is only used for GitLab? I believe we are only using designteam from a practical, everyday perspective. We can probably deprecate or retire the designteam-admin group, or rename it to match the new schema if that is possible.
  2. Yes, I think it is best to use the name design instead of matching the designteam FAS group name.
  3. Others could weigh in here, but I think for now, keeping it simple with Owners and Members is all that is needed. Also, it would be great if me, Emma, Madeline, and Julia could be the team owners on Forgejo to start.
_Discussed in [2025-12-08 Design Team meeting](https://discussion.fedoraproject.org/t/fedora-design-team-meeting-2025-12-08-sticker-concepts-fosdem-2026-prep-and-forgejo-migration/176169)_. --- The Design Team uses GitLab as our forge of choice at the moment. We discussed this in our meeting, and had a few questions of our own: 1. For GitLab migrations, is it possible to migrate issues to Forgejo, including the sequence of issue numbers? Will we need to change our numbering system? 2. Is there any support for GitLab Epics? The Design Team heavily uses epics in GitLab and it would help to know whether these will migrate over somehow, or if we have to leave them behind. 3. Will design assets, like image uploads and files, will those move from GitLab to Forgejo? Here is some of my perspective to Ryan's clarifying questions: 1. I think `designteam-admin` is only used for GitLab? I believe we are only using `designteam` from a practical, everyday perspective. We can probably deprecate or retire the `designteam-admin` group, or rename it to match the new schema if that is possible. 2. Yes, I think it is best to use the name `design` instead of matching the `designteam` FAS group name. 3. Others could weigh in here, but I think for now, keeping it simple with Owners and Members is all that is needed. Also, it would be great if me, Emma, Madeline, and Julia could be the team owners on Forgejo to start.
t0xic0der commented 2025-12-10 03:17:23 +00:00
Author
Member
Copy link

For GitLab migrations, is it possible to migrate issues to Forgejo, including the sequence of issue numbers? Will we need to change our numbering system?

The numbering is retained on successful migration.

Is there any support for GitLab Epics? The Design Team heavily uses epics in GitLab and it would help to know whether these will migrate over somehow, or if we have to leave them behind.

Any cross references among the tickets, like dependencies or epics, might not be as Forgejo does not support Epic types.

Will design assets, like image uploads and files, will those move from GitLab to Forgejo?

We engineered a script to do it post-migration. See #276.

Also, as the Fedora Design team is doing floating migration, I think that it makes sense to close out the older tickets on the source namespace as they get completed and create newer ones on the destination namespace as time goes on.

> For GitLab migrations, is it possible to migrate issues to Forgejo, including the sequence of issue numbers? Will we need to change our numbering system? The numbering is retained on successful migration. > Is there any support for GitLab Epics? The Design Team heavily uses epics in GitLab and it would help to know whether these will migrate over somehow, or if we have to leave them behind. Any cross references among the tickets, like dependencies or epics, might not be as Forgejo does not support Epic types. > Will design assets, like image uploads and files, will those move from GitLab to Forgejo? We engineered a script to do it post-migration. See #276. Also, as the Fedora Design team is doing floating migration, I think that it makes sense to close out the older tickets on the source namespace as they get completed and create newer ones on the destination namespace as time goes on.
t0xic0der added this to the Sprint 12 project 2025-12-10 03:21:16 +00:00
t0xic0der modified the project from Sprint 12 to (deleted) 2026-01-12 10:57:47 +00:00
ryanlerch modified the project from (deleted) to Sprint 12 2026-01-12 11:05:07 +00:00
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 12
Assignees
Clear assignees
No assignees
t0xic0der
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#276 Write a script to move attachments from GitLab to Forgejo after the migration is done
forge/forge
Reference
forge/forge#313
No description provided.