The ReadME Project: Put the Contributors Behind the Product in View

Read the campaign story

GitHub introduced The ReadME Project on 20 August 2020 as a place for the open-source community’s personal and professional stories. The launch named its first featured contributors and invited nominations. It centred experiences behind the software rather than only announcing features. In May 2021, GitHub added The ReadME Podcast, initially hosted by Brian Douglas and Kathy Korevec. The written and audio forms remain one programme family in this case.

The announcements establish a community editorial initiative and its intended subject matter. They do not prove that recognition increased contributor income, reduced maintenance burdens or caused more software contributions. The selected profiles should not be treated as a representative sample of everyone working in open source. This study analyses the communication design while keeping a story’s visibility separate from material support for the person featured.

Editorial interpretation: users may know a project name without knowing the people who maintain it or the decisions that keep it useful. A profile gives that work context and can make its human costs easier to understand. The platform’s role is to provide attention and distribution, but the story should retain the contributor’s perspective rather than always resolving into praise for the host company.

A nomination mechanism can broaden the editorial pipeline, yet it can also favour already visible people. The team needs an intentional approach to finding less prominent forms of contribution and to handling the attention a profile creates. Recognition is most credible when the participant can choose what remains private and when the publication does not imply that exposure is adequate compensation for ongoing labour.

Explain the contribution before celebrating the personality

Show what the person actually does, why it matters and which collaborators share the work. Avoid making a complex project seem like the achievement of a lone hero. A clear account of documentation, review, coordination or maintenance can expand the audience’s understanding of valuable contribution. Check technical details with the participant and other appropriate records, while keeping personal experience clearly attributed rather than presenting it as a universal community condition.

Give participants control over personal boundaries

Explain the audience, format, editing process and likely reuse before the interview. Let contributors decline questions unrelated to the public work. Do not require a hardship narrative to make someone worth featuring. Agree on factual review and correction procedures, and consider how increased visibility could affect contact volume or unwanted attention. The editorial team should have a response plan if a contributor is harassed or a detail is misunderstood after publication.

Connect recognition with realistic next steps

Link readers to the participant’s approved project information and explain appropriate ways to learn more or contribute. Do not direct an unprepared audience to flood a maintainer with requests. Ask whether the attention serves the project’s stated needs and whether existing contribution guidance is ready. Where financial support is mentioned, distinguish it from editorial coverage and verify the destination. The profile should improve understanding, not simply transfer a sponsor’s engagement target into somebody else’s unpaid workload.

A small test for another brief

A local professional association publishes three consent-based profiles of overlooked adult contributors to a shared community resource, with each participant approving the practical contact route.

Measure understanding of the contribution, participant experience, appropriate referrals and unwanted-contact burden. Keep readership separate from financial support or actual project participation.

Pause if a participant feels pressured, factual disagreements remain unresolved or attention creates a burden the project cannot manage.

• Choose varied forms of contribution and explain the selection process.
• Agree on personal boundaries, factual review and reuse before recording.
• Publish clear project context and a manageable next step for interested readers.