Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collecting Statistics from Users #190

Open
AndreyNikiforov opened this issue Oct 26, 2020 · 4 comments
Open

Collecting Statistics from Users #190

AndreyNikiforov opened this issue Oct 26, 2020 · 4 comments

Comments

@AndreyNikiforov
Copy link
Collaborator

To better understand how our software is used, it would be very beneficial to collect analytics from the field. Based on that data we'll decide what features can be sunset and which worth more support.

Is there a free service for open source software that support that kind of analytics?

Example:

  • collect runtime versions, avg download speed
  • analytics outcome: nobody uses python lower than 3.8 and avg download speed 100M
  • possible decisions:
    • drop python prior 3.8
    • low priority for partial downloads work
@menkej
Copy link
Collaborator

menkej commented Oct 26, 2020

I can understand the intention but I have a bad feeling about programs that "call home" in any way...

I suggest talking about a roadmap regarding supported python versions and make priority of work connected to the things where we have the most "activity" or request by users. Not everything someone would like makes sense. We should focus on the stuff we're using and if someone really wants something be open for pull requests - or, if it interests one of us - lend a hand...

@AndreyNikiforov
Copy link
Collaborator Author

I can understand the intention but I have a bad feeling about programs that "call home" in any way...

Yes, it can be a sensitive subject. Being open about intend and transparent about implementation may help. This functionality may be opt-in or opt-out.

I suggest talking about a roadmap regarding supported python versions and make priority of work connected to the things where we have the most "activity" or request by users. Not everything someone would like makes sense. We should focus on the stuff we're using and if someone really wants something be open for pull requests - or, if it interests one of us - lend a hand...

"Most activity" is the challenge. So far we can only judge by the number of issues, which shows problem areas out of used.

Let's keep ideas and discussion going.

@ndbroadbent
Copy link
Collaborator

I also have mixed feelings about it, but I know Homebrew has some analytics: https://docs.brew.sh/Analytics

It looks like they just use Google Analytics. There are some privacy-focused analytics companies out there like Plausible, but I think they don't support events for this kind of use-case (just page views).

I think crash reporting with something like Sentry could also be extremely valuable

@AndreyNikiforov
Copy link
Collaborator Author

I looked at homebrew -- nice note explaining what and why. Has controls to turn analytics on/off. Opt-in on first run.

Thinking of the pattern that may resonate with icloudpd users well:

  • opt-in on first run; short motivation/explanation
  • documented and easily accessible controls
  • transparency 1 -- show data that was sent and when
  • transparency 2 -- show results from analytics (on the web site)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants