Skip to main content
Cwgordon7 Notes on Drupal, testing, and open source

Archive note

Open participation is a habit, not a launch

Thoughts on contributor programs, newcomer friction, and the unglamorous work of keeping a community open.

2 min readCharlie GordonField notebook

Every open project has a stated welcome and an actual welcome. The stated one lives on a page. The actual one is the experience of a newcomer trying to find a task, run the code, and get a reply.

Participation is a queue of small permissions

Before someone can contribute, they need permission to ask a question, permission to try, permission to be wrong in public, and permission to take up review time. A participation program that only addresses the first one produces enthusiasm without progress.

The practical work is to shorten the distance between "I would like to help" and "here is a task I can finish today". That distance is made of documentation, labelled issues, and a person who answers.

Newcomer tasks should be real tasks

A task that exists only to keep a newcomer busy teaches them that the project does not trust them. A real task, even a small one, teaches the shape of the codebase and the standards of review. The best first tasks are useful, bounded, and connected to someone who will respond.

If a task would not be worth a maintainer's time, it is not worth a newcomer's time either.

Review capacity is the bottleneck

Projects often recruit contributors faster than they can review. The result is a growing queue and a fading welcome. Before launching a participation push, check who will read the work. If the answer is "whoever has time", the push will create frustration on both sides.

A named reviewer, even for a few hours a week, changes the experience. It gives newcomers a person to ask and gives the project a predictable pace. The contributor guide is a good model because it sets expectations before the first patch.

Make the habit visible

Participation is not a launch event. It is a set of routines: a weekly triage, a first task label, a template for asking good questions, and a public note about what changed. These are unglamorous and they compound.

The measure of success is not the number of people who say hello. It is the number who come back with a second contribution, and the number who eventually help someone else find their first.