You can edit almost every page by Creating an account and confirming your email.

Forgejo

From EverybodyWiki Bios & Wiki








Forgejo
A screenshot of a Forgejo repository
A screenshot of a Forgejo repository
Initial release{{#statements:inception|from=Q115962387}}
Written inGo, JavaScript
Engine
    Operating systemCross-platform
    Platformx86-64, ARM
    Available inMulti-lingual[1]
    TypeCollaborative software development (forge)
    License{{#statements:copyright license|from=Q115962387}}
    Website{{#statements:official website|from=Q115962387}}

    Search Forgejo on Amazon.

    Forgejo (eo)[2] is a software package designed for hosting a forge using the Git version control system to aid with software development. The package allows developers to use collaborative features like bug tracking, code review, continuous integration, kanban boards, issue tracking system tickets, and wikis with their projects.[3] The package is designed to be self-hosted by developers, and a public instance is provided to try out the software, however forges that are hosted by organizations such as Codeberg are more commonly used. Forgejo can be hosted on all platforms that support the Go runtime, including macOS and Microsoft Windows, and packages are provided for various Linux distributions.[4][5][6]

    History

    Forgejo was initially created in December 2022[7] as a fork of Gitea. The fork occurred after a for-profit limited corporation ran by the lead maintainer of the project, Lunny Xiao, silently transferred Gitea's trademarks and operations to the company and began to establish an open-core model.[8][9]

    Following the discovery of the transfer, many Gitea contributors signed an open letter asking for the project's trademarks and domains to be placed under community management,[10] but after the company rejected to transfer the properties, those contributors chose to fork the codebase.[9] Codeberg, one of the major forges using Gitea at the time, migrated to Forgejo and has become the de jure lead maintainers of the project.[11][12]

    Hard fork and license change

    While initially being a soft fork (a fork that remains synchronized with its upstream counterpart), Forgejo eventually abandoned the practice and split from Gitea following version 1.21 in February 2024, as maintaining compatibility with Gitea became more complex as new features and changes were implemented that were not compatible with Forgejo, as well as to liberate software development from the shackles of proprietary tools.[13]

    In August 2024, Forgejo moved from the MIT license to the copyleft GNU General Public License.[14][15] This does not involve a re-licensing of the existing codebase, but rather reflects a community decision made a year prior that Forgejo would begin to accept GPL-licensed contributions.[16] As a result, the license of the overall package is now reflected to be covered under the GPL.

    Interoperability between forges

    One of the main goals for the future of Forgejo is their plan to implement interoperability between different installations. While repositories can be mirrored from any other Git forge, the project has begun work on implementing support for the ActivityPub protocol, allowing users to collaborate with each other using Forgejo's features.[17] The project has received funding from the NLnet organization for both the protocol extension needed to accommodate the feature subset, dubbed as "ForgeFed", and its implementation into Forgejo.[18][19] As of 2025, the ability to federate "stars" on repositories across Forgejo installations has been built,[20] while other forge packages such as GitLab have also begun work on implementing support for ForgeFed.[21]

    Users

    While Codeberg is known as being the largest server running Forgejo and is one of the project's primary contributors, the Fedora Linux project has begun to adopt the software for their code forge, moving away from the previous forge software, Pagure.[22][23]

    Following the use of Copilot by GitHub, some people have moved to Codeberg or self-hosting Forgejo.[24]

    See also

    References

    1. "Codeberg Translate". Codeberg.
    2. "Forgejo FAQ | Forgejo – Beyond coding. We forge". forgejo.org.
    3. Edenhauser, Markus (October 26, 2023). Git trifft Mikrocontroller, Dein umfassender Guide zur Versionierung in Arduino-Projekten inkl. GitHub Beispiele (in Deutsch). Selbstverlag. p. 9.1. ISBN 9783757972936. Search this book on
    4. "Packaging". Delightful Forgejo. Retrieved 2024-08-23.
    5. "Versions for forgejo". Repology. Retrieved 2024-08-23.
    6. "GitHub Copilot on autopilot as community complaints persist". Archived from the original on 2025-09-06. Retrieved 2025-09-06. Unknown parameter |url-status= ignored (help)
    7. "Beyond Coding. We forge". Forgejo Blog. 2022-12-15. Retrieved 2024-08-23.
    8. "Forgejo FAQ | Forgejo – Beyond coding. We forge". forgejo.org. Retrieved 2023-09-17.
    9. 9.0 9.1 Tietze, Christian (November 25, 2022). "Gitea Ltd. Takes Over Gitea Open Source Project, Community Pushes Back". christiantietze.de. Archived from the original on February 12, 2023. Retrieved February 12, 2023. Unknown parameter |url-status= ignored (help)
    10. "Open Letter to Gitea". 2022-10-28. Archived from the original on 2022-10-31. Retrieved 2024-08-23. Unknown parameter |url-status= ignored (help)
    11. "Codeberg launches Forgejo". Codeberg.org. December 15, 2022. Archived from the original on February 8, 2023. Retrieved February 8, 2023. Unknown parameter |url-status= ignored (help)
    12. "New Git repository faces corporate open source doubts | TechTarget". Software Quality. Retrieved 2024-05-27.
    13. Brockmeier, Joe (23 February 2024). "Forgejo makes a full break from Gitea [LWN.net]". LWN.net. Retrieved 2024-02-27.
    14. "Forgejo is now copyleft, just like Git". Forgejo Blog. 2024-08-22. Retrieved 2024-08-23.
    15. Alden, Daroc (23 August 2024). "Forgejo changes license to GPLv3+ [LWN.net]". lwn.net. Retrieved 2025-01-17.
    16. Warren, Earl (2023-04-18). "[Mission] on Forgejo accepting copyleft contributions". forgejo/governance – Codeberg.org. Retrieved 2024-08-23.
    17. Berre, Daniel Le (2023-11-15). Higher Education and Research Forges in France - Definition, uses, limitations encountered and needs analysis (report thesis). Comité pour la science ouverte.
    18. "NLnet; ForgeFed". nlnet.nl. Retrieved 2025-01-17.
    19. "NLnet; Federated software forges with Forgejo". nlnet.nl. Retrieved 2025-01-17.
    20. "Show and Tell: Federation at Forgejo". fosdem.org. Retrieved 2025-03-08.
    21. "Support ActivityPub for GitLab (&11247) · Epics · GitLab.org · GitLab". GitLab. Retrieved 2024-07-16.
    22. amoloney (2024-12-24). "Fedora Chooses Forgejo!". Fedora Community Blog. Retrieved 2025-01-17.
    23. Brockmeier, Joe (4 December 2024). "Fedora moves towards Forgejo (Fedora Magazine) [LWN.net]". lwn.net. Retrieved 2025-01-17.
    24. Claburn, Thomas (2025-09-05). "Let us git rid of it, angry GitHub users say of forced Copilot features". The Register. Retrieved 2025-09-07.

    External links


    This article "Forgejo" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Forgejo. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.