Measuring first-contribution time without gaming the metric

Pageviews on the contributor guide tell you almost nothing about whether the guide works. The useful measure is the time from first clone to a merged change that a maintainer considers useful, for someone who has not worked in the repository before.

That number should not become a race. Shortening it by removing necessary checks or by pairing every newcomer with a senior engineer hides broken steps. The goal is to find friction that documentation can remove.

In dry-runs we ask a volunteer to follow only the written path. They may ask clarifying questions, but maintainers answer by improving the guide rather than whispering side instructions. Stuck points become tickets against specific paragraphs.

Common blockers include outdated install commands, missing environment variable lists, and contribution checklists that assume prior knowledge of release branches. Each is cheap to fix once observed.

After a rewrite, run one more dry-run with a different volunteer. If the second person stalls in a new place, you have uncovered the next layer. Keep iterating until the written path matches the working path.