Comparison of source-code-hosting facilities
Wikimedia list article
A source-code-hosting facility (also known as forge software) is a file archive and web hosting facility for source code of software, documentation, web pages, and other works, accessible either publicly or privately. They are often used by open-source software projects and other multi-developer projects to maintain revision and version history, or version control. Many repositories provide a bug tracking system, and offer release management, mailing lists, and wiki-based project documentation. Software authors generally retain their copyright when software is posted to a code hosting facilities.
General information
Features
Version control systems
Popularity
Discontinued: CodePlex, Gna!, Google Code.
Specialized hosting facilities
The following are open-source software hosting facilities that only serve a specific narrowly focused community or technology.
Former hosting facilities
Alioth (Debian) – In 2018, Alioth has been replaced by a GitLab based solution hosted on salsa.debian.org. Alioth has been finally switched off in June 2018.
BerliOS – abandoned in April 2014
Betavine – abandoned somewhere in 2015.
CodeHaus – shut down in May 2015
CodePlex – shut down in December 2017.
Begin with the source’s own compact description: “Comparison of source-code-hosting facilities” is wikimedia list article. The dossier treats that line as a proposition to test through Comparison, source-code-hosting and facilities, not as a finished interpretation.
Why this record matters
The phrase “wikimedia list article” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 4, 2026. The linked authority identifier is Q2495946. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2018, 2014, 2015 and 2017.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Comparison of source-code-hosting facilities”, its source revision and the description used here.
- Expand the search: follow Comparison of source-code-hosting facilities primary sources, Comparison of source-code-hosting facilities archive and Comparison research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Comparison of source-code-hosting facilities”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Comparison of source-code-hosting facilities” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.