Forgejo migration tracker #35
Labels
No labels
Contributors' Guidance
Improve written Material
Contributors' Guidance
technical support measures
effort
high
effort
low
effort
medium
good first issue
help wanted
meeting topic
needs changes
needs reporter feedback
needs review
priority
high
priority
low
priority
medium
priority
on hold
type/content
type/misc
No milestone
No project
No assignees
4 participants
Notifications
Due date
Dependencies
No dependencies set.
Reference
docs/tickets#35
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 tracks progress of docs migration to Forgejo. It only concerns repositories we actively publish on docs.fp.o, not archives.
Still needs migrating:
In Gitlab (not so urgent but still should be migrated):
These are on github; owners may want to keep them there but we might still want to ping them:
For bootc docs, this would likely happen as part of migrating the whole organization from GitLab to Fedora Forge.
For FCOS docs, I am not aware of any plans to migrate repos from GitHub to Fedora Forge, but I'll ask the team.
@hricky Thank you for that info.
main#37Moving this issue from the 2026 Q2 Team Goals milestone to 2026 Q3 Team Goals. The Q2 milestone is closing out at the end of June with 10 of 13 issues completed. Significant progress was made on this tracker during Q2, with the majority of Pagure repositories now migrated.
As a reminder, the hard deadline for Pagure.io repositories is 31 July 2026. I've updated the issue due date to reflect this. Any remaining Pagure.io repositories that need to be migrated should ideally be moved over before that date. For repos where migration isn't practical or where the content is no longer actively maintained, we should consider moving them to the archived org instead.
For the remaining GitLab repositories, I'd suggest we open separate planning tickets. These migrations have more moving pieces and unique challenges (e.g. CI pipelines, org-level migrations like bootc) that deserve their own tracking rather than being bundled into this checklist.
Regarding the i3wm SIG docs: I'm volunteering to help with the Fedora i3 SIG Docs migration, given my past role with the team as a maintainer. I've also posted a call for help to the i3wm SIG to find out whether the community wants to continue building the Spin in Fedora Linux 45:
The response to that outreach will help decide whether we migrate the i3 docs repo to Forgejo or archive it. I'm targeting the end of July for a decision on the i3wm docs site.
Assisted-by: Claude Opus 4.6 (1M context)
For the i3 SIG docs repo, see forge/forge#641. @x3mboy is working on the migration.
I talked to @huzaifas about the Defensive Coding Guide, he says he'll get it done by end of the month (the current pagure deadline) and that he'll ping me if he needs anything. I also asked him to open an issue in https://forge.fedoraproject.org/security/tickets/issues so it's tracked in some other location than my head.
The repos on Gitlab all have issues opened asking to migrate already, but noone reacted to them except for the one in Legal. I'll have to find responsible parties and ping them directly.