Summary
Add a lightweight measurement checklist so growth efforts can be evaluated by real adoption signals, not just stars.
Scope
Create a markdown doc such as docs/marketing/measurement.md or docs/project/visibility-metrics.md that defines what to track weekly:
- GitHub stars, forks, watchers.
- GitHub traffic: views, clones, referrers.
- PyPI downloads, if available.
- Docker pulls, if available.
- Docs traffic/Search Console, if available.
- Discussions/issues/PRs from non-maintainers.
- External mentions/backlinks.
Why this matters
If Shorts, articles, community posts, and ads are tested later, the repo needs a consistent way to judge what actually produced useful traffic and adoption.
Acceptance criteria
- Measurement doc exists and is linked from a maintainer-facing docs area.
- Includes a simple weekly table template.
- Includes recommended UTM conventions for links from social/blog/ads.
- Separates vanity metrics from adoption/contribution metrics.
Summary
Add a lightweight measurement checklist so growth efforts can be evaluated by real adoption signals, not just stars.
Scope
Create a markdown doc such as
docs/marketing/measurement.mdordocs/project/visibility-metrics.mdthat defines what to track weekly:Why this matters
If Shorts, articles, community posts, and ads are tested later, the repo needs a consistent way to judge what actually produced useful traffic and adoption.
Acceptance criteria