Manifesto by Homebrew maintainer Mike McQuaid arguing OSS maintenance on company time is infrastructure work, not theft, and requires no manager approval.
Key Takeaways
Companies depend on OSS daily but rarely classify maintenance as work; McQuaid says maintainers should treat it as technical debt and just do it.
Practical guardrails: verify your employment contract, negotiate an IP carve-out before signing, and keep company confidential data strictly separate.
GitHub’s Balanced Employee IP Agreement (CC0-licensed) is cited as a concrete template to request by name when negotiating.
The argument is weakest for junior or precarious engineers and anywhere time is billed to specific clients, grants, or regulated projects.
Alternatives endorsed but framed as insufficient: Open Source Pledge ($2,000/dev/year) and Open Source Friday (2 hrs/week).
Hacker News Comment Review
Framing matters in practice: commenters with employer buy-in got it by pitching OSS contribution as free expert review and zero future maintenance cost, not charity.
IP ownership is the sharpest real obstacle: in most jurisdictions, code written during work hours belongs to the employer, and getting formal OSS release approval through legal can take months and often stalls completely.
A minority pushed back on the ethics entirely, arguing permissive licenses already grant companies the right to consume without contributing, so the moral case for unilateral action is weaker than the manifesto claims.
Notable Comments
@jcalvinowens: Reframe the ask as “free expert review and zero future maintenance cost” to get blanket employer permission with minimal friction.
@tonymet: “brought to you by the unemployed, or soon to be unemployed and sued” – sharp dissent on legal exposure.
