> [!question] Lingering Questions > - What is the twelve-month retention rate by on-ramp type? The talk describes entrances thoroughly and says nothing about who stays. > - What is the baseline for the "more than double the female representation" claim among Japanese Kubestronauts? > - Would the Weir open-review model work without a self-selected expert audience already reading the comments? > [!tip] Article Ideas > - "You're not underqualified, you're differently qualified" — contribution onboarding piece built on the none-of-the-contributors-were-writers frame. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Credential Screens Select for the Proxy Not the Work]] — same reading batch, complementary claim: that note is about a filter removing capable people; this source's claim is about capable people removing *themselves* by measuring against the wrong skill > - [[3. Resources/Permanent Notes/Coding Fatigue as Enemy Attack Removes the Option to Rest]] (Erika Kirk deep-read) — contrast worth holding: healthy communities in this source offer multiple entrances *and*, per that note, need a legitimate exit — this source only covers the entrance half > [!quote] Vocabulary > - **Kubestronaut** — CNCF certification-completion program with a status marker (jackets); "golden status" is a higher tier > - **clotributor.dev** — CNCF's good-first-issue finder, tagged by language and specialty > - **Leave No Trace** — camping ethic the speaker extends to open-source and conference participation: minimize impact, clean up after others, leave it better than found ## Bib capsule Twelve-minute KubeCon Japan 2026 opening keynote by a CNCF employee, using the self-published serialization and reader-corrected drafting of Andy Weir's *The Martian* as an extended analogy for open-source contribution, followed by concrete on-ramps and Japan-specific community growth data. ## Author's thesis Open-source contribution is fundamentally about community ownership of an idea rather than code mechanics, and the people who improve a project bring expertise the maintainer lacks rather than a lesser version of the maintainer's own skill — illustrated by *The Martian*'s reader-scientists correcting Weir's orbital mechanics and chemistry despite none of them being writers. Concrete on-ramps should be matched to contributor disposition (mentorship, certification, advocacy, meetups) rather than assuming one archetype, and momentum accumulates from small, individually invisible acts rather than single large pushes. ## Key arguments 1. **Cross-expertise contribution**: none of the people who improved *The Martian* were writers — they contributed domain expertise (chemistry, orbital mechanics) the author lacked, reframing the contribution barrier from "am I good enough at what they do" to "do I know something they don't." 2. **Maintainer discretion is part of the model, not an obstacle to it**: Weir merged "the good ones" and deliberately kept one known mathematical error because the resulting explosion was load-bearing for the plot. 3. **Disposition-matched on-ramps widen the contributor base**: mentorship for quiet learners, certification for overachievers, advocacy for extroverts, meetups for everyone — a deliberate departure from assuming a single social archetype for contributors. ## Claim atoms ### Contributors supply expertise the maintainer lacks, not a weaker version of it > [!quote] ID: rw_sica-cloudnative-2026 > Here's the part that I love the most. None of the contributors were writers. Where/why: ~00:03:30 — the keynote's genuine insight, relocating the contribution barrier from skill-matching to difference. New Permanent below. ### Communities that offer one entry path recruit only one temperament Where/why: ~00:05:30 — mentorship / certification / advocacy / meetups matched explicitly to different dispositions. New Permanent below. ### Filing an issue is itself a contribution Where/why: ~00:11:30 — directly addresses the fear of wasting maintainer time that keeps first-time contributors from acting. Held; close enough to existing vault thinking on contribution pathways to connect rather than duplicate. ## Permanent candidates - **Cross-expertise contribution** — promoted below. - **Disposition-matched on-ramps** — promoted below. ## Processing checklist - [x] Ported claim atoms and verbatim quotes from the existing deep-read - [x] Checked existing Permanents for duplication — none found on either promoted claim - [x] Created two new Permanent notes - [x] Connected into relevant MOC ## Metadata - Source: [[3. Resources/Readwise/Full Document Contents/Articles/Where Will Cloud Native Take You - Jeffrey Sica, Cloud Native Computing Foundation]] - is_nar_related: false ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — direct fit for contribution-pathway design and maintainer discretion - [[3. Resources/MOCs/DevRel MOC]] — disposition-matched onboarding is directly applicable community-program design