-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Pkg3: telemetry #29
Comments
In terms of actual implementation, inspiration could be taken from Homebrew, which has opt-out telemetry and is MIT licensed (so there's no need to worry about derived works). |
A few thoughts on this;
|
Note that if Pkg3 downloads tarballs rather than git clones we might also be able to get download counts via GitHub releases. |
@simonbyrne You can already get info in git clone counts, as it is, from github. http://stackoverflow.com/a/38217108/179081 However it is only counters -- not information about the OS, julia version etc. |
Very happy to see this discussion. I just want to chime in to say the following: this kind of telemetry could be very useful for developers that are considering to do breaking changes. Will also be a good indication to know whether you need deprecations or even an announcement. |
I'd like to see Pkg3 support some kind of anonymized opt-out telemetry.
For example, it could keep track of statistics like like how many times
Pkg.add
has been called for a given package with a heuristic to not count CI testing. This would give us a more reliable guide of package popularity than github stars.The text was updated successfully, but these errors were encountered: