I’ve been tinkering with version control again lately and tried many project management tools, but it wasn’t until this year that I seriously started selecting a specific tool. As for why Fimacode Repository’s code hosting system uses Forgejo instead of Gitea, there isn’t much to discuss — I tried both software several years ago, and since Forgejo is a fork of Gitea, there isn’t much difference.
It wasn’t until early last year, when Forgejo decided to proceed with a hard fork, that I started paying attention to this project again.
Gitea actually originally forked from Gogs as well, and later developed rapidly thanks to its strong development team, gaining its current market share.
One of the reasons we ultimately chose Forgejo is that Gitea already has a large market share, which has even spread to the Chinese region. If we plan to offer a series of commercial projects in the future and our underlying infrastructure needs to depend on it, we must ensure a complete and reliable foundational software supply chain.
Forgejo isn’t perfect, but it’s sufficient for the current stage of building the Wenpai ecosystem.
The ultimate goal of Wenpai is also to develop an independent version based on WordPress that suits domestic users. Forgejo can serve as a development model for forking open-source projects — using it while experimenting and learning.