I’ve been tinkering with version control again lately and have tried many project management tools. It wasn’t until this year that I seriously started selecting a specific tool. As for why the code hosting system for Firma’s repository 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 a huge difference.
It wasn’t until early last year, when Forgejo decided to proceed with a hard fork, that I started paying attention to the project again.
Gitea itself originally forked from Gogs. It later developed rapidly, thanks to a strong development team, which led to its current market share.
One of the reasons we ultimately chose Forgejo is precisely because Gitea’s market share has grown significantly and has even spread to the Chinese region. If we plan to offer a series of commercial projects in the future, and the underlying infrastructure depends on this, we must ensure a complete and reliable foundational software supply chain.
Forgejo isn’t perfect, but it’s sufficient for the current stage of Wenpai’s ecosystem development.
Wenpai’s ultimate goal is to develop an independent version based on WordPress that suits domestic users. Forgejo can serve as a model for the development of an open-source project branch, allowing us to use, experiment, and learn simultaneously.