Draft:SourceHut
From Wikipedia, the free encyclopedia
SourceHut is a suite of software entangling a software forge developed by Drew DeVault and its contributors. It features, primarily, a handful of tools, such as mailing lists, bug/feature tickets, continuous integration/continuous delivery service, and manual pages, integrated into a single Software as a Service. The main version control system is git, with Mercurial as a community-run project. The project is fully libre/free software, and mostly done in the open, including infrastructure packages and toolings.
Submission declined on 10 February 2026 by Rambley (talk).
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
|  |
| SourceHut | |
|---|---|
 | |
| Developers | SourceHut and its contributors |
| Initial release | 2017 |
| Written in | Python, Go and JavaScript |
| Available in | English |
| License | AGPL License, BSD License[1][1] |
| Website | https://sourcehut.org |
History
The project started in February 2017 by North-American programmer Drew DeVault as a side project written in Python, using Flask, Bootstrap, PostgreSQL, and licensed under GNU General Public License version 2.
Eventually, the project shifted from using Python and a REST API structure to GraphQL, and Go as an intermediary tool for core services.
In early 2021, the suite also gained the ability to host static pages[2], similar to GitHub Pages. In the same year, it also introduced a persistent IRC bouncer service[3], as an option for software maintainers to have a direct channel for offering support for their users/projects.
Also, up to early 2020, the project tracked and published its quarterly financial reports, but eventually slowed down to yearly reports.[4]
SourceHut also created forgeperf, a tool to track down and index software forge's performance[5], which boosted the interest in collaboration for performance issues on other software forges such as Codeberg and GitLab[6].
The project also earned a grant from NLnet NGI Zero fund around 2021, spurring developments across their projects.
By mid 2024, the project moved its infrastructure to Europe due to DDoS attacks[7], and around the same time next year, it started accepting the Euro as a payment method.
Comparison
The main aspect of SourceHut when compared with other forge software is that it heavily focuses on mailing lists, and/or patches as a collaboration model, which is the default model of Git.
The project also tries a more conservative approach to design and lightweightness, by relying mostly on server-side rendering and almost no JavaScript pages. The rationale for that is offering low-end users the ability to use SourceHut's services.[8]
Lastly, the project also takes a different approach to its maintenance of community projects, such as inviting users from the community to maintain base images for CI/CD builds, and other projects hosted in the SourceHut infrastructure, such as the already mentioned Mercurial support.
Components
The fundamental software that underpins GitHub is Git itself, written by Linus Torvalds. However, community-run projects, such as Mercurial support, are available. The project has a strong focus on mailing-list or patch-derived contributions; hence, SourceHut offers automatic mailing-list integration with their build software and git.
A non-extensive list of components is:
- git.sr.ht - Git hosting
- builds.sr.ht - CI/CD
- man.sr.ht - Manual pages
- todo.sr.ht - Ticket tracker
- lists.sr.ht - Mailing-lists
- hg.sr.ht - Mercurial hosting
- chat.sr.ht - IRC bouncer support
- provide significant coverage: discuss the subject in detail, not just brief mentions or routine announcements;
- are reliable: from reputable outlets with editorial oversight;
- are independent: not connected to the subject, such as interviews, press releases, the subject's own website, or sponsored content.
Please add references that meet all three of these criteria. If none exist, the subject is not yet suitable for Wikipedia.