Developers of the Forgejo collaborative development platform announced about changing the development model. Instead of maintaining a synchronized fork of Gitea, the Forgejo project has now branched into a completely independent codebase that will evolve on its own and follow its own path. It is noted that the full fork is the culmination of the divergence of the development and management models of Forgejo and Gitea.
Project Forgejo arose in October 22 as a result of a “soft” fork of Gitea. Hosting powered by Forgejo Codeberg.org. The project code is written in Go and supplied under MIT license. The fork was created in response to attempts to commercialize Gitea and transfer control to a commercial company. Forgejo has continued to practice independent governance and maintain community ownership. Until now, Forgejo has regularly migrated all Gitea code changes, but also added its own new features that are not available in Gitea. The more native features were added to Forgejo, the more complex the process of keeping codebases in sync became.
Advertisement
Full decoupling will make it easier to maintain, promote new functionality, and fix bugs, as well as speed up the reduction of technology debt and save resources spent on analyzing conflicts with changes appearing in the Gitea codebase. The cost of a full fork would be that Forgejo would not be able to be used as a transparent replacement for Gitea, and would make it more difficult to migrate from Gitea to Forgejo. However, the Forgejo API will remain compatible with the Gitea API whenever possible.
Thanks for reading: