Add analytics for package download and other stats

Open
#976 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
build-system, cli

Research direction

The issue names no files, tests, or entry points. First clarify the analytics scope, anonymous data requirements, collection point, and privacy expectations; the work is done when the project has an agreed design and implementation plan for the requested package, backend, compiler, and project statistics.

Written by the indexing model from the issue text.

Description

RFC

We should collect anonymous analytics (much like brew does it), so that we'd get some insight about things like:

  • how popular packages are
  • how popular alternate backends are
  • what version of the compiler folks use
  • what kind of projects people build (single package, multipackage, etc)
  • etc.
Dominant language
PureScript
Stars
831
Forks
137
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from purescript/spago

All issues in purescript/spago

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.