Projects migrating to Forgejo

Thousands of projects around the world are happy users of Forgejo, they are using it every day to develop awesome free/libre software, run it for their homelab or in their company.

However, we acknowledge that not everyone is able to use Forgejo today. This repository intends to track potential migrations to Forgejo in these cases:

• Projects that would like to migrate to Forgejo, but are facing challenges (for example due to missing features or because they require assistance for the social aspects of moving a large project).
• Projects that want to move from their current solution, but are not yet decided where to go.
• Projects that are considering to use Forgejo and would like to track the advantages of Forgejo over their current solution.

Intended usage of this place

Here, we aim to help you ease the migration. If you have a project (or know some) that is considering a migration (to Forgejo), please file an issue so we can track it and have a discussion here.

Please help us understand how we can ease a migration and making a decision for you. Providing details helps a lot, feel free to reference discussions happening in your spaces as well.

Please respect projects that do not use Forgejo

We ask everyone to maintain a respectful tone and respect project's decisions not to use Forgejo (yet). While you might disagree to their opinion and are free to provide arguments or helpful advice, this place is not meant to be used as a battleground across projects.

We acknowledge that there are other valid choices next to Forgejo that can have their own advantages. Further, due to vendor lock-in, not all projects can move to Forgejo easily, and migrations of large projects require significant effort and coordination to not disrupt the project's development itself.

Especially the support for proprietary integrations (think of building software for proprietary operating systems) can be a blocker for migration to Forgejo, because Forgejo is only officially supporting free/libre software. However, the community is open to provide solutions and workarounds to break free of proprietary dependencies.