Open-source infrastructure, built in the open.
Contributor curves across major open-source projects show a familiar shape: a spike of first-time pull requests, then a cliff. We propose treating onboarding as an instrumented funnel — and fixing the leakiest step before recruiting anyone else.
GitHub Sponsors, OpenCollective, and foundation grants all promise to sustain open source — but the ledgers tell a more complicated story. We break down where the money actually lands, what each dollar buys, and why burnout, not bandwidth, is where most funding goes to die.
Every repository has one — the issue that outlives maintainers, frameworks, and sometimes entire companies. We trace a single nine-year-old bug report through its forks, workarounds, and 400-plus comments to understand what stale tickets really cost an open-source project.
When a CVE lands, the clock starts before most maintainers have finished reading the report. This timeline traces how real projects spend their first 24 hours — and where the difference between containment and chaos takes root.
Most open-source decisions are made in threads that no one will ever read again. This piece examines what happens when governance artifacts vanish into scroll-depth oblivion — and proposes treating them like the documentation they already are.
Every public RFC, open maintainer meeting, and visible roadmap is engineering time spent with a maintainer's hat in hand rather than on a keyboard. We break down where those hours actually go and argue that 'built in the open' deserves a line item in the project plan, not a footnote in the README.
Nobody ever chose a library because of a landing page hero. From the quickstart to the migration guide, these are the documentation surfaces doing the quiet work of converting, retaining, and de-risking — and each one has a job description most projects never write down.
Every build tree contains libraries whose last meaningful commit predates the last three framework releases. This hands-on guide walks through auditing abandoned dependencies — reading commit history like an archaeologist, spotting red flags, and deciding whether to adopt, replace, or vendor.
The word 'stable' carries wildly different meanings depending on who is reading your release page. We argue that projects owe their users an explicit stability contract — written down, versioned, and enforceable — instead of a semver badge that means everything and nothing.
When a popular open-source project fractures, downstream developers inherit the argument. Here is a practical rubric — governance, cadence, roadmap divergence, and maintainer incentives — for deciding which branch earns your commits and your dependencies.
Semantic versioning reads like arithmetic but behaves like a contract. This piece examines why breaking changes succeed or fail on the human communication wrapped around the number — and what maintainers owe the engineers downstream.
When a founding maintainer steps back, the vacuum they leave behind is rarely filled by good intentions alone. This article dissects real governance transitions, the quiet failure modes of committee rule, and a concrete playbook for projects planning their own handoff.
A version number is a contract, but most projects forget the other clauses. This piece examines how disciplined deprecation windows, compatibility shims, and honest changelogs keep downstream teams from being blindsided by breaking changes.
Semantic versioning is less a numbering scheme than a social contract, and the contract is only as strong as a project's track record. This piece argues that 'stable' is a claim about behavior over time, sketches a deprecation policy that enterprise adopters can actually plan around, and makes the case for breaking things slowly.
The changelog is the most-read document in an open-source project, yet it gets less care than the README. We trace how a single vague entry can ripple into a production incident and lay out a practical discipline for writing, conventioning, and automating release notes without draining them of human judgment.
A README is the airlock between the outside world and your codebase — and most projects weld it shut. We reviewed hundreds of open-source repositories to identify the seven documentation failures that quietly drive contributors away, with before-and-after fixes for each.
Shipping a major version of an open-source project is less a launch and more a controlled demolition. Here's the full, unvarnished timeline of how Asterix v3.0 went from a contentious RFC to a signed release tag — and what your team can steal from our pipeline.