CACrown ArchivesThe cinema collection
Menu
Research dossier · Science & Nature

GForge

forge software originally forked from SourceForge Alexandria 2.6

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionMay 13, 2026
Entity authorityQ3104748
Source-derived summary

GForge is a commercial service originally based on the Alexandria software behind SourceForge, a web-based project management and collaboration system which was licensed under the GPL. Open source versions of the GForge code were released from 2002 to 2009, at which point the company behind GForge focused on their proprietary service offering which provides project hosting, version control (CVS, Subversion, Git), code reviews, ticketing (issues, support), release management, continuous integration and messaging. The FusionForge project emerged in 2009 to pull together open-source development efforts from the variety of software forks which had sprung up.

History

In 1999, VA Linux hired four developers, including Tim Perdue (1974-2011), to develop the SourceForge.net service to encourage open-source development and support the Open Source developer community. SourceForge.net services were offered free of charge to any Open Source project team. Following the SourceForge launch on November 17, 1999, the free software community rapidly took advantage of SourceForge.net, and traffic and users grew very quickly.

As another competitive web service, "Server 51", was being readied for launch, VA Linux released the source code for the sourceforge.net web site on January 14, 2000, as a marketing ploy to show that SourceForge was 'more open source'. Many companies began installing and using it themselves and contacting VA Linux for professional services to set up and use the software. However, their pricing was so unrealistic, they had few customers. By 2001, the company's Linux hardware business had collapsed in the dotcom bust. The company was renamed to VA Software and called the closed codebase SourceForge Enterprise Edition to try to force some of the large companies to purchase licenses.

Editorial summary

The public source identifies “GForge” as forge software originally forked from SourceForge Alexandria 2.6. This brief keeps that definition visible, then builds a research path around GForge, forge and software.

Editorial reviewA practical orientation to terminology and classification, particularly when read beside dated observations, specimens or technical literature. The current lead gives the account dated anchors—2002, 2009, 1999, 1974—that can be checked directly. The linked authority record independently contributes the date 2006. Its value is orientation rather than verdict, with GForge, forge and software providing the first useful test.
Editorial analysis

Why this record matters

A short description can identify a subject without explaining its stakes. For “GForge”, the useful work is to connect “forge software originally forked from SourceForge Alexandria 2.6” to the records capable of establishing context and consequence.

Evidence profile

Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated May 13, 2026. The linked authority identifier is Q3104748. 3 of 4 selected statements include explicit references; 3 carry qualifiers and 0 use preferred rank. The first chronological checks are 2002, 2009, 1999 and 1974.

Critical limits

Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. 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

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “GForge”, its source revision and the description used here.
  2. Expand the search: follow GForge primary sources, GForge archive and GForge research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “GForge”?
  2. Is the terminology current, historical or disputed?
  3. Has classification or technical consensus changed since the cited source?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from GForge” 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.