# A Contributor's Value Is Expertise the Maintainer Lacks ## Claim A contributor's usefulness comes from bringing knowledge the project's creator doesn't have, not from performing a weaker version of the creator's own skill, so the right eligibility question is "do I know something they don't" rather than "am I as good as them at what they do." <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Applies to open, community-improvable work of any kind — software, writing, documentation — where the creator retains merge/editorial authority over externally offered corrections. - The reframe doesn't remove the need for judgment: the creator (or maintainer) still decides which contributions to accept, including declining technically-correct fixes that don't serve the work. - Doesn't establish that this mechanism is what makes a project succeed — a single success story illustrates the mechanism without proving it's sufficient or necessary for success. - Breaks where the project genuinely requires uniform, single-domain expertise throughout (a narrow technical spec with no cross-domain surface) — the reframe has less to offer where there's no different expertise to bring. ## Evidence Andy Weir serialized *The Martian* free on his website after publisher rejection. His readers were chemists and physicists, not novelists, and they filed what amounted to bug reports against his orbital mechanics and chemistry — wrong burn rates, incorrect hydrazine behavior. He incorporated the corrections he judged worth incorporating and deliberately kept one known mathematical error because the resulting explosion was load-bearing for the plot. Jeffrey Sica's framing: "None of the contributors were writers" — they contributed a different expertise entirely, and a separate group of readers contributed only enthusiasm ("when's the next chapter?") that kept him producing. ## Links - [[DevRel MOC]] — what a contributor is actually for, which reframes how projects should recruit - [[3. Resources/Permanent Notes/Credential Screens Select for the Proxy Not the Work]] — because contrasts; that claim is about an institutional filter removing capable people from consideration, this one is about capable people removing themselves by measuring their eligibility against the wrong skill - [[3. Resources/Permanent Notes/Casual Contributors Are Users Not Community Members]] — because applies-in; both concern where the line falls between someone who merely uses/consumes a project and someone whose input genuinely shapes it - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; contribution-pathway design and onboarding messaging are directly downstream of this reframe ## Tests / falsifiers - Compare a project's contribution rate before and after it explicitly recruits for domain-adjacent expertise (rather than core-skill matches) — a null change would weaken the claim's practical import. - Find a project where non-domain-matched contributors introduced more errors than they caught, on net — this would bound the claim to cases where the outside expertise is genuinely relevant to a specific gap. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/Where Will Cloud Native Take You]] — reports the Andy Weir/*The Martian* serialization story as the source's central illustration.