Draft:Forgejo

{{AFC submission|d|web|u=LemurianPatriot|ns=118|decliner=Caleb Stanford|declinets=20250308211812|ts=20250117043225}}

{{AFC submission|d|v|u=Ahri.boy|ns=118|decliner=SafariScribe|declinets=20240919040607|small=yes|ts=20240607132513}}

{{AFC comment|1=Too many forgejo.org and Forgejo Blog citations. Please use fewer primary sources so as to demonstrate that the topic is deemed notable by independent, reliable sources.

The article doesn't provide sufficient context to someone not familiar with the topic on why the topic is independently notable.

There are some sentences like: "A future objective of Forgejo is to utilize the ActivityPub protocol (known for its usage in the fediverse) to federate forges via ForgeFed" which seem like too much detailed information for a Wikipedia article and of unclear relevance to readers.

There is a citation error: "Missing or empty title" (please fix). Caleb Stanford (talk) 21:18, 8 March 2025 (UTC)}}

{{AFC comment|1=Note to AFC Reviewers: This draft is for a title that was previously an article, but was then cut down to a redirect. If this draft is accepted, the history should be preserved. Do not tag the redirect for G6.

If you find that this draft should be accepted, and do not have the Page Mover privilege, please request assistance in moving the redirect to preserve the history.

Reviewers should check the history and verify whether there was a consensus to cut the article down to a redirect, or whether the action was taken boldly without discussion. If there was a consensus for the cutdown, do not accept this draft without verifying that the draft improves the article or that consensus has changed. If in doubt, please discuss.

There have been articles at Forgejo only briefly, that were cut down to redirects by their authors. Robert McClenon (talk) 19:54, 9 June 2024 (UTC)}}

----

{{Infobox software

| qid = Q115962387

| logo = Forgejo-wordmark.svg

| logo size =

| logo caption =

| screenshot = Forgejo screenshot dark mode.png

| caption = A screenshot of a Forgejo repository

| released = {{#statements:inception|from=Q115962387}}

| latest release version = {{wikidata|property|edit|reference|P348|eid=Q115962387}}

| latest release date = {{wikidata|qualifier|P348|P577|eid=Q115962387}}

| programming language = Go, JavaScript

| operating system = Cross-platform

| platform = x86-64, ARM

| language = Multi-lingual{{cite web |url=https://translate.codeberg.org/projects/forgejo/forgejo/ |title=Codeberg Translate |website=Codeberg}}

| genre = Collaborative software development (forge)

| license = {{#statements:copyright license|from=Q115962387}}

| website = {{#statements:official website|from=Q115962387}}

}}

Forgejo ({{IPA|eo|forˈd͡ʒe.jo}}){{Cite web|url=https://forgejo.org/faq/|title=Forgejo FAQ | Forgejo – Beyond coding. We forge.|website=forgejo.org}} 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.{{Cite book |title=Git trifft Mikrocontroller, Dein umfassender Guide zur Versionierung in Arduino-Projekten inkl. GitHub Beispiele |date=October 26, 2023 |isbn=9783757972936 |pages=9.1 |language=de |last1=Edenhauser |first1=Markus |publisher=Selbstverlag }} 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.{{Cite web |title=Packaging |url=https://codeberg.org/forgejo-contrib/delightful-forgejo#packaging |access-date=2024-08-23 |website=Delightful Forgejo}}{{Cite web |title=Versions for forgejo |url=https://repology.org/project/forgejo/versions |access-date=2024-08-23 |website=Repology}}

History

Forgejo was initially created in December 2022{{Cite web |date=2022-12-15 |title=Beyond Coding. We forge. |url=https://forgejo.org/2022-12-15-hello-forgejo/ |access-date=2024-08-23 |website=Forgejo Blog}} 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.{{Cite web |title=Forgejo FAQ {{!}} Forgejo – Beyond coding. We forge. |url=https://forgejo.org/faq/#why-was-forgejo-created |access-date=2023-09-17 |website=forgejo.org |language=en}}{{Cite web |last=Tietze |first=Christian |date=November 25, 2022 |title=Gitea Ltd. Takes Over Gitea Open Source Project, Community Pushes Back |url=https://christiantietze.de/posts/2022/11/gitea-ltd-takes-over-open-source-community-pushes-back/ |url-status=live |archive-url=https://web.archive.org/web/20230212021254/https://christiantietze.de/posts/2022/11/gitea-ltd-takes-over-open-source-community-pushes-back/ |archive-date=February 12, 2023 |access-date=February 12, 2023 |website=christiantietze.de}}

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,{{Cite web |date=2022-10-28 |title=Open Letter to Gitea |url=https://gitea-open-letter.coding.social/ |url-status=deviated |archive-url=https://web.archive.org/web/20221031061345/https://gitea-open-letter.coding.social/ |archive-date=2022-10-31 |access-date=2024-08-23}} but after the company rejected to transfer the properties, those contributors chose to fork the codebase. 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.{{Cite web |date=December 15, 2022 |title=Codeberg launches Forgejo |url=https://blog.codeberg.org/codeberg-launches-forgejo.html |url-status=live |archive-url=https://web.archive.org/web/20230208001911/https://blog.codeberg.org/codeberg-launches-forgejo.html |archive-date=February 8, 2023 |access-date=February 8, 2023 |website=Codeberg.org}}{{Cite web |title=New Git repository faces corporate open source doubts {{!}} TechTarget |url=https://www.techtarget.com/searchsoftwarequality/news/366552837/New-Git-repository-faces-corporate-open-source-doubts |access-date=2024-05-27 |website=Software Quality |language=en}}

= 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.{{Cite web |title=Forgejo makes a full break from Gitea [LWN.net] |url=https://lwn.net/SubscriberLink/963095/85db4f864c060d22/ |access-date=2024-02-27 |website=LWN.net}}

In August 2024, Forgejo moved from the MIT license to the copyleft GNU General Public License.{{Cite web |date=2024-08-22 |title=Forgejo is now copyleft, just like Git |url=https://forgejo.org/2024-08-gpl/ |access-date=2024-08-23 |website=Forgejo Blog}}{{Cite web |title=Forgejo changes license to GPLv3+ [LWN.net] |url=https://lwn.net/Articles/986998/ |access-date=2025-01-17 |website=lwn.net}} 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.{{Cite web |last1=Warren |first1=Earl |date=2023-04-18 |title=[Mission] on Forgejo accepting copyleft contributions |url=https://codeberg.org/forgejo/governance/pulls/20 |access-date=2024-08-23 |website=forgejo/governance – Codeberg.org}} 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.{{Cite thesis |title=Higher Education and Research Forges in France - Definition, uses, limitations encountered and needs analysis |url=https://hal-lara.archives-ouvertes.fr/hal-04208924 |publisher=Comité pour la science ouverte |date=2023-11-15 |degree=report |language=en |first=Daniel Le |last=Berre}} 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.{{Cite web |title=NLnet; ForgeFed |url=https://nlnet.nl/project/ForgeFed/ |access-date=2025-01-17 |website=nlnet.nl}}{{Cite web |title=NLnet; Federated software forges with Forgejo |url=https://nlnet.nl/project/Federated-Forgejo/ |access-date=2025-01-17 |website=nlnet.nl}} As of 2025, the ability to federate "stars" on repositories across Forgejo installations has been built,{{Cite web |title=Show and Tell: Federation at Forgejo |url=https://fosdem.org/2025/schedule/event/fosdem-2025-5610-show-and-tell-federation-at-forgejo/ |access-date=2025-03-08 |website=fosdem.org |language=en}} while other forge packages such as GitLab have also begun work on implementing support for ForgeFed.{{Cite web |title=Support ActivityPub for GitLab (&11247) · Epics · GitLab.org · GitLab |url=https://gitlab.com/groups/gitlab-org/-/epics/11247 |access-date=2024-07-16 |website=GitLab |language=en}}

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.{{Cite web |last=amoloney |date=2024-12-24 |title=Fedora Chooses Forgejo! |url=https://communityblog.fedoraproject.org/fedora-chooses-forgejo/ |access-date=2025-01-17 |website=Fedora Community Blog |language=en-US}}{{Cite web |title=Fedora moves towards Forgejo (Fedora Magazine) [LWN.net] |url=https://lwn.net/Articles/1000751/ |access-date=2025-01-17 |website=lwn.net}}