OctoPrint / OctoPrint/plugins.octoprint.org
[Feature Request] historical adoption metrics
Nobody has claimed this yet.
- Dominant language
- Less
- Stars
- 144
- Forks
- 370
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 3
Description
What do you want to see implemented in the plugin repository?
I'd like to see some longer historical data around plugin adoption, to complement the 7-day and 30-day active user metrics already published.
It would be fantastic if there were multiple historical dumps of weekly/monthly plugin stats, in addition to the current json dumps in https://data.octoprint.org/export/. Even something as simple as "copy the current json files into a /yyyy/mm/dd/*.json folder" run once a week would be enough to do some manual analysis.
Even cooler would be a graph on each plugin page that shows how adoption has trended over time.
Why, what problems would be solved by this?
The "new installs" and "active instances" stats sections to the right of each plugin are great! But as a plugin maintainer, I'd like to know more about how my plugin has performed over time - whether adoption is growing or shrinking, and by how much.
With this information, I can see if my development effort has been worthwhile, or if people are losing interest / leaving for something else.
Any additional information you want to provide?
Happy to help contribute to make this happen, although I haven't been able to see how the data export stuff works from a brief search through octoprint's repositories.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current JSON dumps in https://data.octoprint.org/export/ and the existing 7-day and 30-day adoption metrics. Define whether the first deliverable is dated weekly or monthly JSON history, plugin-page trend graphs, or both; done means historical adoption can be compared over time.
Written by the indexing model from the issue text.
Assessment
- Domain
- analytics, data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100