Proposal: migrate FSKY Forge to Gitea #2

Closed
opened 2025-08-03 00:03:35 +02:00 by architect · 1 comment
Owner

FSKY Forge is running Forgejo, a fork of the popular self-hosted software forge Gitea. It was created as a protest fork after Gitea has been incorporated with the goal of offering hosting services using specialized versions of Gitea.

During its early days, Forgejo has not diverged much from Gitea and migrating between them was possible. However, this has changed.

Forgejo has decided to become a hard fork and make migration between the two Git forges impossible. Commits from Gitea are cherry-picked and only few make it to Forgejo. As a consequence, a lot of new features, bug fixes and UI/UX improvements from Gitea have never made it to Forgejo, with no plan of ever porting them.

This is starting to get very frustrating for FSKY as some issues that affect us remain unfixed and features from Gitea that we take for granted are missing in Forgejo with no progress made to port them. It offers no useful benefits over Gitea.

As much as we want to migrate to Gitea, it is impossible to do it in a safe way as Forgejo chose to break backwards compatibility. This means FSKY Forge would have to start fresh and users would have to (mostly) manually migrate to the new Gitea instance. Thankfully, Forgejo and Gitea offer a way to easily migrate individual repositories between forges, preserving everything including issues and pull requests.

As this would be a very big change, it is up to the FSKY Forge community to decide on it.

FSKY Forge is running Forgejo, a fork of the popular self-hosted software forge Gitea. It was created as a protest fork after Gitea has been incorporated with the goal of offering hosting services using specialized versions of Gitea. During its early days, Forgejo has not diverged much from Gitea and migrating between them was possible. However, this has changed. Forgejo has decided to become a hard fork and make migration between the two Git forges impossible. Commits from Gitea are cherry-picked and only few make it to Forgejo. As a consequence, a lot of new features, bug fixes and UI/UX improvements from Gitea have never made it to Forgejo, with no plan of ever porting them. This is starting to get very frustrating for FSKY as some issues that affect us remain unfixed and features from Gitea that we take for granted are missing in Forgejo with no progress made to port them. It offers no useful benefits over Gitea. As much as we want to migrate to Gitea, it is impossible to do it in a safe way as Forgejo chose to break backwards compatibility. This means FSKY Forge would have to start fresh and users would have to (mostly) manually migrate to the new Gitea instance. Thankfully, Forgejo and Gitea offer a way to easily migrate individual repositories between forges, preserving everything including issues and pull requests. As this would be a very big change, it is up to the FSKY Forge community to decide on it.
architect added the due date 2025-08-20 2025-08-03 00:08:35 +02:00
Author
Owner

The poll has been concluded.

The poll has been concluded.
architect locked as Resolved and limited conversation to collaborators 2025-08-20 03:17:09 +02:00
This discussion has been locked. Commenting is limited to contributors.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2025-08-20

Dependencies

No dependencies set.

Reference: fsky/governance#2
No description provided.