# Communities With One Entry Path Recruit Only One Temperament ## Claim A community that offers a single way to get involved recruits only the temperament suited to that specific path, so matching multiple on-ramps to different dispositions widens the contributor base without lowering the bar for any of them. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Applies to volunteer, contributor, and community-membership programs where initial engagement style varies meaningfully by personality (comfort with public visibility, preference for structured achievement vs. open-ended exploration, etc.). - The claim is about breadth of recruitment, not depth of commitment — offering more entry paths doesn't by itself say anything about retention or conversion to deeper roles. - Doesn't specify how many paths are enough, or which dispositions matter most for a given community — the source names four (quiet learners, overachievers, extroverts, generalists) without claiming that taxonomy is exhaustive. - Breaks where a community genuinely has only one viable participation mode (e.g., a project with no non-code surface at all) — the design principle needs multiple genuine paths to exist before it can be applied. ## Evidence Jeffrey Sica describes CNCF's contributor on-ramps as deliberately disposition-matched rather than singular: mentorship (pairing through a first commit) for "quiet learners," the Kubestronaut certification program (with a visible status marker — jackets) for "overachievers," the Ambassador program for extroverts and advocacy-inclined people, and local meetups as the shared entry point for everyone. He grounds the design in his own counterfactual: he and a friend attended a local meetup, met someone already in the Kubernetes community, and were pulled into the project — "if we had not met that person at our local meetup, none of this would happen." ## Links - [[Open Source Governance MOC]] — how a single onboarding route silently selects who ends up in the project - [[3. Resources/Permanent Notes/A Contributor's Value Is Expertise the Maintainer Lacks]] — because extends; from the same source, both concern lowering barriers to entry by matching the program to who the person actually is rather than assuming a single ideal-contributor profile - [[3. Resources/Permanent Notes/Coding Fatigue as Enemy Attack Removes the Option to Rest]] — because contrasts; that note is about a healthy community needing a legitimate exit, this one is about needing legitimate entrances — together they bound a full lifecycle a community design should account for - [[3. Resources/MOCs/DevRel MOC]] — because applies-in; contributor program design is core DevRel practice ## Tests / falsifiers - Compare contributor diversity (by self-reported disposition or engagement style) between a program with multiple matched on-ramps and a comparable program with a single generic on-ramp — no measurable difference would weaken the claim. - Track twelve-month retention by on-ramp type — if all paths convert to sustained contribution at similar rates, that would support treating them as equally valid entrances rather than a tiered funnel; if one path dominates conversion, the "widens the base without lowering the standard" framing needs qualification. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/Where Will Cloud Native Take You]] — reports CNCF's four named on-ramps and the speaker's own meetup counterfactual.