search

smartin015 / continuousprint

Octoprint plugin to allow the creation of a print queue that prints, clears the bed and then prints again
40 stars 38 forks source link

Better user reporting flow #163

Closed smartin015 closed 2 years ago

smartin015 commented 2 years ago

Is your feature request related to a problem? Please describe.

I don't know who's using which features of CPQ, nor how. This limits my ability to preemptively solve problems and to focus on what matters to the most people - instead I only know what matters to the minority of folks who know how to report issues on github.

Describe the solution you'd like

I'd like something that answers the following questions, but which also preserves user anonymity and choice to contribute this information:

  1. In what driver state do CPQ errors/exceptions most frequently occur?
  2. How many users are using network queues? How many devices are connected per queue?
  3. How many jobs do folks have in their queue? What's the distribution of sets per job?
  4. Are set qualifiers - like material settings and print profiles - commonly set for prints?
  5. How frequently does profile inference resolve to a specific printer?
  6. Are Obico and SpoolManager often installed alongside CPQ so that integrations are enabled?
  7. How many instances are using the release candidate branch? How often do they get updated?
  8. How many users have any scripts at all that are set for specific events? (e.g. bed clearing)
  9. How many users use non-default scripts and preprocessors (new features in 2.3.0)
  10. How much time does CPQ spend in each state, in aggregate? e.g. do a lot of folks just leave it idle, or inactive?

I'm imagining something like:

From that, I can do data analysis to get approximate answers to the above questions.

Describe alternatives you've considered

A user survey could also work, but that requires active effort and seems unlikely to get a large sample size.

Additional context

The "Anonymous Usage Tracking" settings page of OctoPrint seems like a fine example to follow for CPQ's own anonymous tracking setup.

smartin015 commented 2 years ago

Maybe we just reduce friction for the user to request changes / report bugs. That way there's less infra to maintain and less user data collection concerns.