Since the discussion about the change proposal triggered so many replies (some of those implying malevolence in moving the discussion from ML to Discourse and split in separate threads), let’s get down to the core question and make use of the advanced feature of Discourse to have users clearly state their willingness to FESCO. Please don’t add more comments here, just use this thread for vote. As the proposal clearly state that submitters are not interested in OPT-IN (off by default) metrics, …
A poll like this is never going to be representative, unfortunately.
No matter what, you’ll always have a vocal minority that are against telemetry, despite the fact you can turn it off or block it.
The question always comes back down to, how good do you want the product to be/how much room for improvement is there?
In order to deliver the best products possible, it means being able to identify issues and telemetry does that.
I am someone who would turn it on to help the project, but I do understand the concerns of those who want this to be opt-in. My recommendation is for no default behavior whatsoever. A great compromise is an explicit two button option that cannot be skipped by the user. One button sets telemetry on, while the other sets it off. This seems to be a great compromise, without any default behavior.
Cassidy James Blaede suggested some excellent wording in his post. I am in favor of that or something similar.
You’ll still have the people who are opposed to any telemetry at all, but I think that would do a lot to alleviate the concerns.
The issue there is that the majority of users don’t change preferences. And for telemetry to be useful, it needs to be on by default to capture as much info as possible.
The issue is resolved by my proposal.
