The developers of the collaborative development platform Forgejo have announced a change in their 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.
The Forgejo project was created in October 22 as a result of a soft fork of Gitea. Forgejo operates Hosting Codeberg.org. The project's code is written in Go and licensed under the MIT license. The fork was created in response to attempts to commercialize Gitea and transfer control to a commercial company. Forgejo continued to apply the principles of independent governance and maintained community control. Until now, Forgejo has regularly migrated all Gitea code changes, but has also added its own new features not found in Gitea. The more features added to Forgejo, the more complex the process of codebase synchronization became.
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.
Source: opennet.ru
