GNU Telephony: Preserving a Free-Software Web Legacy

Open-source software can outlive the websites that first introduced it. Source code may still be downloadable, but historical release notes, documentation, user guides and links in old mailing lists may point to domains or files that no longer work. Restoring access requires more than placing a new homepage at an old address. It requires understanding which project the material belongs to, where authoritative sources remain available and what a modern preservation effort can responsibly claim.

GNU Telephony is an instructive example. Its historical website, gnutelephony.org, was associated with free-software telephony and related technical documentation. TwoSquares is developing an independent website and documentation preservation effort around this legacy material. This article describes the preservation approach and current source references; it is not an announcement that every legacy file has been recovered, that the software has been relaunched or that TwoSquares is the official GNU maintainer.

What was GNU Telephony?

The GNU Project describes GNU Telephony as part of the GnuComm telecom subsystem, supporting free-software telephony and communications. The GNU pages identify software associated with this ecosystem, including GNU Bayonne, GNU SIP Witch, GNU Common C++/uCommon, GNU ccAudio, GNU ccScript, GNU ccRTP and ZRTP-related components.

The official GNU Telephony overview and GNU SIP Witch documentation are the appropriate starting points for project descriptions and current GNU-hosted references. GNU's own pages also acknowledge that some information was recovered from historical web archives. That makes the wider problem concrete: archived documentation can become valuable to an established software community when the original project portal changes or disappears.

Why historical documentation is difficult to preserve

A long-running software project rarely consists of a single website. Technical references may be spread across a wiki, developer pages, generated API documentation, downloadable source archives, issue trackers and third-party references. Older links may contain unusual query strings, versioned paths or subdomains tied to servers that no longer exist.

For GNU Telephony, relevant historical URL families include project wiki entries, versioned downloads, technical documents and references to components such as ccRTP, Common C++ and SIP Witch. Each file or page needs individual verification. A modern index of preserved documents must indicate the project, the version, the source and whether the item is original or reconstructed.

Preservation approach: evidence before reconstruction

Identify historical demand

Start from links in documentation and research pages. A reference to a Common C++ class manual suggests a need for the exact versioned API information; a generic marketing page cannot satisfy it. Archive the requested path, surrounding anchor text and original target where possible.

Locate authoritative sources

Check the GNU Project's GnuComm documentation, GNU software downloads, relevant Savannah repositories and archived snapshots before recreating a page. Use original released files where available and respect software and documentation licences.

Preserve version and provenance

Do not silently mix interfaces from different releases. Record whether a package is a historical source archive, an API reference generated from a particular release, a community note or newly written guidance. A reproducible manifest should contain source locations, capture dates and integrity checks for preserved binaries where possible.

Rebuild navigable explanations

Visitors may need introductory context to understand an older codebase. New editorial material can explain what the components did, how they related and why particular documents matter. It should be labelled as new commentary, distinct from original documentation and from any official GNU publication.

Restore links selectively

Where a historical URL can be served with the same authorised file, that is often preferable to changing its meaning. When an original document has an equivalent modern location, use a direct relevant redirect. When the material is absent, provide a useful source record or an accurate missing-document response, not an unrelated homepage.

A practical demonstration of digital preservation problems

This effort illustrates challenges that also affect commercial websites: domain changes, versioned downloads, inaccessible knowledge bases, disappeared authors and inconsistent URL structures. The common requirement is a trustworthy inventory and a clear record of what has actually been recovered.

The Digital Curation Exchange historical record addresses a different kind of vanished resource, an academic and professional knowledge portal. The two subjects connect through the methods, not through an institutional relationship: inventories, provenance, preservation metadata, source discovery and responsible access.

Businesses facing related problems can learn more about website restoration, legacy software documentation preservation and SEO migration.

Current status and limitations

The historic GNU ecosystem and its official source references are independently documented. A complete, verified inventory of the materials recoverable from the former gnutelephony.org portal is not yet included on this page. No number of recovered files, functional software builds, restored links or formal partnership is claimed here. As individual resources become available and are checked, they should be documented on the project site with original paths, version details, source citations, licences and change history.

This distinction protects both readers and the original contributors. Independent preservation is not project maintainership, and owning a domain is not ownership of the software or its documentation.

FAQ

Is GNU Telephony a GNU project?

The official GNU site describes GNU Telephony within the GnuComm subsystem. The independent TwoSquares preservation activity is not the GNU Project itself.

Are GNU Telephony packages available from official sources?

The GNU software download page provides package and mirror information. Check the relevant software pages for versions, dependencies and licence terms.

Is TwoSquares relaunching GNU SIP Witch?

No software relaunch is asserted here. The scope described is website and documentation preservation, with exact recovered assets to be verified individually.

Can old links be redirected to this article?

Only if they genuinely referred to an overview or preservation explanation. Links to specific code archives, API references or documentation files should resolve to those materials or to precise source records instead.

Primary sources