Notes on the second-chance economy

The 2026 open source crisis isn't a funding problem. It's an attention problem. AI-generated PRs, GitHub Copilot suggestions that aren't reviewed, and the maintainer who has to triage all of it. The data, the patterns, and what to do about it.

MIT, Apache 2.0, BSD, GPL, AGPL, BSL, SSPL, Elastic — which license should you pick? The 2026 decision tree, with the maintainer-handoff angle.

The first-contribution playbook. Find a project, set up the dev environment, find a good first issue, submit a PR, respond to review. The path from zero to a real commit history.

Documentation is the artefact that survives the handoff. This guide covers the 6 documents every OSS project should have, plus the 2 documents that make a maintainer handoff possible.

A 12-point checklist for evaluating an open source project before depending on it. Bus factor, license, maintenance signals, security, and the soft signals that predict long-term viability.

The maintainer's guide to PR review. The 5-step review workflow, how to be welcoming to first-time contributors, and how to handle the bad PRs (spam, AI slop, drive-by).

The four governance models for open source projects. BDFL (Python, before), foundation (Linux Foundation, Apache), vendor-led (Kubernetes), community-led (PostgreSQL). How each affects the maintainer handoff.

BSL, SSPL, Elastic — the new wave of source-available licenses. How they differ from open source, why HashiCorp and MongoDB moved, and what it means for adoption.

A great release note is one that a new maintainer can read 6 months later and know exactly what to work on. The format, the tone, the structure, and the cut-a-release checklist.

The README is the first thing the next maintainer reads. It sets the tone for everything. The 7 sections every README should have, the 2 sections that make a handoff possible, and the 3 things to never include.

Creative projects (writing, art, music) die differently from code or business. The artifact is the artist's hand. Reviving a creative project means reviving the artist's relationship to the work. This is the playbook.

Motivation is unreliable. These 7 operational tactics will get you to the finish line even when motivation fails. Daily commits, public ship dates, the 10% in 10 days rule, the 5-person review, and more.

Three ways to find abandoned open source projects: GitHub search, the BreakPoint feed, and topic-based scraping. The signals to look for, the keywords to use, the traps to avoid.

5 case studies of real projects that died at 90% complete. A SaaS that almost launched. A novel that almost shipped. A renovation that almost finished. The 90% rule is the most common death pattern for any project. Here's what it looks like in practice.

The 7 distinct reasons people walk away from projects, the psychology behind each, and what they tell you about the original creator. From sunk cost fallacy to identity shifts, the patterns are the same across code, writing, art, and life.

Side projects don't really die. They pause. The sunk cost is too low to formally abandon, the ego attachment is too high to admit defeat, and the spark never fully goes out. This is the case for treating the pause as a feature, not a failure mode.

Handoffs are the most important and least valued economic activity. The maintainer who hands off a project enables the revival. The writer who hands off a manuscript enables the book. Yet handoffs are usually done for free, in private, and without recognition.

There's a hidden economy worth billions in the value of unfinished work. The novel that never sold. The codebase that never shipped. The album that never released. The market for second chances is real, growing, and underserved.

The unfinished novel in a Google Doc. The dormant GitHub repo. The half-built deck in the garage. The half-recorded album on a hard drive. The hidden economy of unfinished work is larger than the GDP of most countries. Here's what it looks like.