
Perpetual Exhibits
A standing room for a project or a life’s work: what it is, why it mattered, who carries it on. Notes for whoever takes it over wait behind the warden.

On display


How to write an exhibit
- One line a stranger understands. Then the story, in your own words.
- Behind the warden: what whoever takes it over should know first, and what they should never change.
- Where the domain, the servers and the accounts are, and who to ask. Never passwords.
- A badge for your successor, so they can show they were chosen.
Still running
Projects whose founder or a core maker is gone, and which others carry on. Facts checked on 2026-10-04, each with a source.
Debian
Thousands of volunteers and a release team keep it going.
Source: DebianBoost C++
Library authors and the community; releases continue.
Source: Boost C++ZeroMQ
An open team still merges fixes and security patches.
Source: ZeroMQNetHack
The NetHack DevTeam still ships releases; 5.0 came out in 2026.
Source: NetHackErlang/OTP
The Erlang/OTP team ships releases; OTP 29.1 came in September 2026.
Source: Erlang/OTPVim
Christian Brabandt and the Vim team; patches land almost daily.
Source: VimAlpine (Pine)
Maintained by Eduardo Chappa, with commits in 2026.
Source: Alpine (Pine)Rake
Maintained by Hiroshi Shibata; v13.4.2 in April 2026.
Source: RakeJ
Jsoftware and its contributors, with commits in 2026.
Source: J
Precedents in the Open Stacks
People made exhibits of their work long before this library. These are on our shelves, free to read.
- Catalogue number 008019 Carmina III.30Odes III.30: A Monument More Lasting than Bronze 23 BCE1 minEN
- Catalogue number 008012 Codicil to the Will of Benjamin FranklinA Loan Fund for Two Hundred Years 17896 min
- Catalogue number 007010 The SQLite blessing, and “SQLite Is Public Domain”The SQLite Blessing 20012 minNo. 38