November 11, 2025
Court of Code: All Rise
Contributing to Open-Source Should Be Required, Like Jury Duty
Internet explodes over “open‑source jury duty” — pay us or back off
TLDR: A writer suggested mandatory open‑source contributions like jury duty. Commenters clapped back: forced patches risk spam and chaos, companies freeload while devs lack time, and some would only show up if paid or trained — spotlighting the real debate over who funds and maintains the software everyone uses.
A developer mused: what if coders got a summons to contribute to open‑source, like jury duty? The idea sent the comment section straight into courtroom cosplay. “All rise for the Honorable Repo!” one joked, while others yelled “git subpoena!” and imagined bailiffs confiscating laptops. The mood: half eye‑roll, half existential crisis.
Strongest takes landed fast. doctorpangloss sneered that it’s already “required” in some projects — people simply avoid those. portaouflop torched the trend of low‑effort patches, griping about “unnecessary AI slob” tacked onto docs. hughes feared a world where maintainers are forced to accept everything, warning of “pure entropy” if quality gates crumble. Then the plot twist: softwaredoug fingered the real culprits as companies, not individual devs — corporate deadlines crush goodwill, and the suits “don’t want to pay any money” while treating community projects like free vendors. That got nods and groans. lawlessone pitched a compromise: summon me if you fund the training.
Drama score: high. Humor score: higher. The core clash is simple and spicy — civic duty versus creative chaos. Is mandatory contribution noble service, or a recipe for spam and burnout? The jury’s still out, but the comments made one verdict clear: if there’s a summons, someone better pick up the tab.
Key Points
- •The author recalls a jury duty summons from seven years ago and reflects on civic participation.
- •They propose an analogy: summoning developers to contribute to open-source as a civic obligation similar to jury duty.
- •The rationale is reciprocity for the benefits developers derive from shared open-source tools and libraries.
- •The author was dismissed from jury service due to connections to the legal field through friends and family.
- •The article references prior related writing (“Good First Issues Are Gifts”) and the influence of reading “Working in Public.”