
Perpetual Exhibits
Work outlives plans. An exhibit keeps a project or a life of work on show: what it is, why it mattered, who carries it on. The notes for whoever takes over sit one layer deeper, behind your warden.
Three layers, your choice in each.
- Public
- The story, the works, the links, who looks after it now.
- Recognised
- A letter to whoever carries it on, the roadmap you never published, where the domain and the servers are and who to ask, a successor badge.
- Sealed
- Anything that needs your keepers: kept offline, opened together.
Apply for an exhibit
Fill in the public part, write what you leave for the right people, set your warden questions. Your browser locks the deeper layer before anything is sent; we never see it.
Go to the front deskListed projects.
Works that are still looked after.
Each of these lost a founder or a core maker, and someone carried on. This is what an exhibit is for. Facts checked on 2026-10-04, each with a source.
The NetHack DevTeam still ships releases; 5.0 came out in 2026.
SourceMaintained by Eduardo Chappa, with commits in 2026.
SourceMaintained by Hiroshi Shibata; v13.4.2 released in April 2026.
SourceThousands of volunteers and a release team keep it going.
SourceAn open team still merges fixes and security patches.
SourceThe Erlang/OTP team at Ericsson; OTP 29.1 shipped in September 2026.
SourceJsoftware and its contributors, with commits in 2026.
SourceChristian Brabandt and the Vim team; patches land almost daily.
SourceName a GitHub successor.
Settings → Account → Successor settings. If you can no longer manage your account, your successor can archive or transfer your public repositories after GitHub checks the situation. They cannot log in as you and do not get your private repositories. Put the rest in your exhibit. GitHub docs
