Apache Attic

Apache Attic The Apache Attic is an archival initiative of the Apache Software Foundation established in 2010 to preserve retired open-source projects. It provides a formal repository for codebases, documentation, mailing lists, and release artifacts that have reached end-of-life status within the Apache community, ensuring continued access for researchers, integrators, and historians of software engineering.

History

The Attic was created by the Apache Software Foundation during a period when projects such as Apache Jakarta subprojects, Apache Avalon, and other legacy efforts reached diminished maintainership, echoing retirements in other ecosystems like SourceForge and GitHub. The decision followed discussions at ASF board meetings and community forums involving contributors from Apache HTTP Server, Apache Tomcat, Apache Ant, and other projects that confronted sustainability challenges similar to those faced by Mozilla Foundation and Eclipse Foundation initiatives. The Attic codified precedents set by informal archives in the early 2000s, reflecting governance patterns observed in organizations such as Free Software Foundation, Open Source Initiative, and Linux Foundation when handling dormant projects.

Purpose and scope

The Attic’s primary purpose is archival stewardship: it accepts projects that the ASF community has voted to retire and preserves their source code, documentation, issue trackers, and mailing list history. Its scope includes legacy codebases formerly hosted under umbrellas like Apache Commons, Apache XML Project, and other Apache top-level and subprojects, paralleling archival aims of institutions like the Internet Archive and repositories maintained by Library of Congress digital preservation efforts. The Attic does not actively develop or maintain released software; instead, it guarantees continued availability for downstream users, researchers, and vendors such as Red Hat, IBM, Google, and Oracle that may need access to historical artifacts. The Attic also serves educational and historical research roles akin to archives curated by Stanford University Libraries and MIT Libraries.

Project retirement process

Projects enter the Attic following a formal retirement workflow codified by the ASF board and project management committees. The process begins with a proposal or request posted to project mailing lists and discussed in public forums involving contributors from projects like Apache Maven, Apache ZooKeeper, Apache Cassandra, and Apache Hadoop. A vote by the project management committee and notification to the ASF board typically precedes a board resolution. The resolution references ASF governance precedents used in decisions about projects such as Apache Struts and Apache Geronimo. Once approved, administrative actions migrate repositories, archives, and mailing list archives into Attic holdings, mirroring archival practices used by National Archives and Records Administration and institutional repositories at universities like University of California systems. The retirement process also documents licensing provenance consistent with licenses promoted by Open Source Initiative and tracking methods used by compliance teams at companies like Microsoft and Amazon Web Services.

Governance and policies

Governance of the Attic aligns with ASF bylaws and the ASF Board’s authority, involving PMC oversight and board resolutions similar to governance interactions observed in Apache License discussions and ASF licensing policy debates. The Attic enforces policies regarding trademark, intellectual property, and contributor license agreements, paralleling standards adopted by organizations such as Creative Commons and Eclipse Foundation. Policy on archival content ensures that retired project artifacts retain their original ASF licensing and copyright notices, a practice comparable to standards used by BSD and MIT licensing ecosystems and mirrored in compliance frameworks used by Debian Project and Fedora Project. The Attic also adheres to transparency practices seen in ASF operations, with public mailing lists and archived minutes similar to those used by bodies like W3C and IETF.

Impact and reception

The Attic has been recognized by developers, historians, and industry stakeholders for providing durable access to legacy code, echoing archival benefits heralded by initiatives such as Internet Archive and academic repositories at Harvard University. Its existence has reduced the risk of code loss for enterprises like Red Hat and IBM that integrate historical components, and supported research into software evolution and technical debt by scholars affiliated with institutions such as Carnegie Mellon University and University of Oxford. Critics and commentators in open-source press outlets including InfoQ, The Register, and Linux Journal have noted that archival alone cannot substitute for active maintenance, citing examples from projects like OpenOffice.org and LibreOffice where forks and community revitalization occurred outside archival paths. Nonetheless, the Attic’s role in preserving provenance and ensuring reproducibility has been cited in legal, academic, and industrial contexts involving software supply chain analysis, compliance reviews by firms like Black Duck Software and Synopsys, and historical studies published by scholars at MIT Press and O’Reilly Media.

Category:Apache Software Foundation