Migrate the DEI team repo to Fedora Forge (Forgejo) #61
Labels
No labels
category
docs
category
meta
category
onboarding
category
outreach
category
physical events
category
virtual events
good first issue
help wanted
needs
changes
needs
reporter feedback
needs
team vote
Priority
High
scope
bug
scope
improvement
scope
new
state
approved
state
blocked
state
duplicate
state
invalid
state
wontfix
No milestone
No project
4 participants
lochipi
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
dei/tickets#61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This ticket will track the effort to migrate the DEI team’s GitLab repo into Fedora’s new home for collaboration (Fedora Forge).
More details about the soft launch here: https://communityblog.fedoraproject.org/announcing-the-soft-launch-of-fedora-forge/
We have a few projects and subgroups under the DEI space here:
If you’d like to help, please comment in this ticket.
assigned to @Lochipi
assigned to @jonatoni
First step: file a ticket with Fedora Infra to create a new organization/team on Forgejo about the DEI team
https://docs.fedoraproject.org/en-US/forge-documentation/requesting_new_org_or_team/#_procedure_filing_a_request_ticket
This ticket came up in our DEI Team meeting discussion today.
In the short-term, @Lochipi will open a Fedora Infra ticket, per the instructions linked above by Jona, to request the DEI Team organization on Forgejo. Additionally, he will also inquire to what sort of migration tooling is available, and if we can help with the migration.
In the meeting, @theprogram and I discussed a bit on whether having the historical issues (e.g. everything here on GitLab) moved over to the same repo for new tickets on Forgejo made sense. My point-of-view was that having the old, historical tickets and the new, ongoing tickets in one repo makes it easier to find context for past decisions while also keeping new discussions in the same place. However, @theprogram mentioned that it could be confusing for newcomers to have everything in one place. I'd like to understand this better!
No, my point was that having three repos is confusing.
We should migrate everything, old historic content and new current content to the Forgejo.
After all content is in one place, we should retire GitLab and Pagure.
Ah, okay. I misunderstood what you meant in the meeting! Fortunately, for the DEI Team, we have already migrated off of Pagure fully to GitLab. So for our team, we are only on GitLab as of now. I think once it is possible for us to make a clean break for Forgejo, we should do so, and promptly phase down our GitLab usage.
Thanks for opening the ticket @Lochipi https://pagure.io/fedora-infrastructure/issue/12860
Discussed in 2025-11-13 DEI Team meeting.
Discussed in 2025-12-11 DEI Team meeting.
During today’s meeting, the team reviewed the progress of the migration to Forgejo, noting that several repositories have already been moved to the new DEI group with a target completion date of late January 2026. It was decided that the "Home” ticket repository will be the last to migrate to ensure continuity during the transition. A specific dependency regarding the Fedora Docs publishing pipeline was identified; the team will coordinate with the Docs Team (specifically @pbokoc) to update the global Antora
site.ymlconfiguration to point to the new repository location. Additionally, the team discussed the value of hosting and recording a video call to demonstrate Forgejo workflows, which would serve as an evergreen educational resource for current and future contributors.The URL in https://gitlab.com/fedora/dei redirecting to Forge included ⚠️s, consider adding a whitespace or something.
Also please consider repeat the above announce in DEI's GitLab repositories as well -- for second I had the wrong assumption dei/a11y and dei/docs were archived without any migration.
Thanks @rffontenelle this is fixed
Done
Thanks.
One more thing: I see docs-fp-o still points to GitLab (same for a11y), so I was wonder if this is tracked as a on-going migration process.
It’s not currently tracked :/ Would you mind opening an issue for this?
Done in #65
Hooray, we made it! We are officially on Forgejo. Thank you @lochipi and @jonatoni for your hard work on seeing this through to completion. I am going to close this ticket as completed. Anything else on Forgejo, we can track as a new ticket.
Closing! 🌊