Hey Neon team, how do you want to implement data collection?

Right out of the gate, I would always opt-in in order to help Neon improve the product and because I have chosen to trust the people behind Neon.

Suggestions:

1) Calamares should have an instance where the user must choose either "YES" or "NO". Neither should be checked by default so that the user be forced to make a conscious decision, or else it should be impossible for the installation to continue. "NO" means "NO", so if one checks "NO", nothing should be sent - not even the info that one has opted out.

2) In case of Multi-level "YES", each should be described specifically and not generically, so the user can understand what each level means.
None should be checked by default so that the user be forced to make a conscious decision, or else it should be impossible for the installation to continue.


It's in the spirit of KDE to deal with this issue in a superior manner to how Ubuntu has so far.

(All for the near future, of course)

Typos are now hopefully corrected. Sorry.

We have an internal policy for data handling already https://community.kde.org/Policies/Telemetry_Policy

apachelogger wrote:We have an internal policy for data handling already https://community.kde.org/Policies/Telemetry_Policy

Sounds good to me. Thank you, Harald.