# Casual Contributors Are Users Not Community Members Raymond's model assumed contributors were intrinsically motivated community members who self-selected for ability. The reality Eghbal describes is different: most people who submit a pull request to an open source project don't want to familiarize themselves with the project's goals, roadmap, or contribution process. They don't think of themselves as part of a "contributor community." They're users who encountered a bug, wrote a fix, and submitted it. They're not joining. They're passing through. This distinction matters enormously for how projects are managed. The "contributor ladder" model assumes casual contributors are community members in training -- that with the right onboarding, mentorship, and encouragement, a drive-by contributor becomes a regular, then a maintainer. Eghbal's data says otherwise: people who become active, long-term contributors were never casual contributors in the first place. They arrived already committed. The conversion funnel that most open source programs build doesn't actually convert anyone. The practical consequence: maintainers spend enormous energy reviewing low-context contributions from people who won't be around to maintain what they submitted. Reviewing a PR from someone who doesn't understand the codebase costs more maintainer time than writing the fix yourself. But rejecting contributions feels hostile, and the open source ethos makes "we don't want your PR" culturally unacceptable. This is a case where a correct mental model changes everything. If casual contributors are users, you treat their PRs like bug reports: appreciate the signal, handle the fix internally. If they're community members, you invest time coaching them. The first protects maintainer attention. The second burns it. <!-- atomicity: 1 idea ✓ --> ## Why This Matters Open source programs that invest heavily in contributor onboarding for casual contributors are optimizing for a conversion that rarely happens. Redirect that investment toward supporting the maintainers who are already committed. ## Links - [[3. Resources/Permanent Notes/Stability Is the Precondition for Formation Across Domains]] — applies-in: community membership forms through repeated participation and relationship, not a single low-commitment contribution - [[3. Resources/Permanent Notes/Stewardship Invests in Contributor Capacity Not Just Cash]] — extends: stewardship turns interested users into durable contributors by investing in mentoring, context, and repeatable paths to responsibility - [[3. Resources/Permanent Notes/Target Audience Determines Translation Methodology More Than Equivalence Theory Does]] — extends: naming the receiving group accurately determines what obligations the producer has toward its knowledge, access, and participation needs - [[3. Resources/Permanent Notes/Open Source Projects Are Not Communities by Default]] — extends: a repository and one-off pull requests remain project use until sustained accountable relationships form. - [[3. Resources/Permanent Notes/Belonging Requires Choice Connection and Progress]] — evidence-for: drive-by contribution remains use rather than membership when choice, connection, and a path of progress never operate together. - [[Active Installs Reward Existing Winners]] — extends: contributor counts and install counts both become misleading when the headline metric is treated as the richer relationship it only approximates. - [[AI Compresses the Knowledge-Worker Pipeline From Both Ends]] — applies-in: a loose pool of drive-by contributors cannot replace the apprenticeship pipeline that produces maintainers with accumulated judgment. - [[3. Resources/Permanent Notes/A Project Is the Community Not the Code]] — qualifies; the community is the project only where participation carries sustained relationships and accountable contribution rather than one-off use. - [[3. Resources/Permanent Notes/The Stadium Is the Dominant Open Source Pattern]] — evidence-for: a small maintainer core surrounded by a large user crowd is the structural result of treating drive-by participation as use rather than membership. - [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]] — extends: low-context contributions consume the scarce judgment of the people who remain accountable for the project. - [[3. Resources/Permanent Notes/The Merit Trap - Self-Worth in Systems of Singular Authority]] — applies-in: treating every submitted contribution as a membership claim adds identity pressure to already concentrated authority. - [[3. Resources/Literature Notes/The Maintainer's Burden - Open Source Beyond the Bazaar - Literature Note]] — source synthesis: the literature note grounds the distinction between transient users and committed maintainers. - [[3. Resources/Permanent Notes/Contribution-Based Education Produces Work-Ready Developers Faster Than Credentials]] — contrasts: authentic contribution can build employable skill without implying that each learner has joined the project's community. - [[3. Resources/Permanent Notes/Default-On AI Activation Inflates Adoption Metrics at the Cost of Consent]] — extends: contributor counts and activation counts both overstate the relationship implied by the headline metric. - [[3. Resources/Permanent Notes/Permissive Licenses Define a Floor But Don't Constitute a Community]] — evidence-for: permission to use or submit code does not create the ongoing relationships and mutual obligations that constitute community - [[3. Resources/Permanent Notes/A Contributor Program Should Ask for the Smallest Next Step Not the Top Role]] — contrasts: write the smallest meaningful ask for each stage of the contributor journey (Sampaio). - [[3. Resources/MOCs/Book Review Synthesis MOC]] — applies-in: the MOC lists it under existing atoms and literature. - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: the MOC lists it under Created, with the point that drive-by PRs don't convert to regular contributors. ## Source - [[3. Resources/Literature Notes/The Maintainer's Burden - Open Source Beyond the Bazaar - Literature Note]] - [[3. Resources/Readwise/Books/Working in Public]] - [[3. Resources/Readwise/Books/The Art of Community|The Art of Community]]