Earlier quoted context omitted.
Let's just be clear that it's entirely OK to add telemetry to your code. The objection here from most of us I suspect is that it is on by default. If you package a tool so it does an unattended installation in some way i.e. via a package manager etc, the default state of the code should be opt-out of telemetry. If you have a GUI installer, ask the user if they want it and outline the benefits and what you collect. If…
Indeed. Though on-by-default telemetry gets a different set of data than engaging with the customer. If adding telemetry is faster and easier than engaging with the customer, then you'll see projects that add telemetry that wouldn't otherwise have the bandwidth to engage with the customer. In general, I think the best way to go is to ask in the installer or initial setup, whether you want to send telemetry, and have…
Here's what we are doing next release (out this week)
* Ask if the user wants to opt out in the graphical installers.
* Print a message after non-graphical installs about data collection and link to documentation on how to turn it off.