Telemetry Policy - Remaining Questions
staniek at kde.org
Mon Apr 30 20:40:10 UTC 2018
On 30 April 2018 at 22:08, Lydia Pintscher <lydia at kde.org> wrote:
> Hey folks,
> * Given that
> GDPR is coming into effect on May 25th I'd like to urge you to
> look into if what you're currently tracking is acceptable under that
> regulation. I don't know how where the data you're collecting currently
> ends up but I don't want the e.V. to be liable for personally identifiable
> information ending up on non-e.V. servers etc.
> * Please make a choice if you're willing to change Kexi to comply with the
> policy or if you prefer it to be marked as a historic exception. (My
> preference is not to have any exceptions to the policy and make a clear
> statement to our users.)
Now we can assume that solution to non-unique identification Volker
explained in acceptable equivalent of random identifiers so KEXI does not
Thanks for patience!
I understand KEXI has time until the next release to switch
to KUserFeedback. In other words, next non-patch release (3.2) would be
compliant and would store data within KDE infra. For 3.1.x we can stop
saving unique random identifiers.
> Everyone: Unless there are big objections within the next week let's
> consider the current draft at
> https://community.kde.org/Policies/Telemetry_Policy accepted.
> Lydia Pintscher - http://about.me/lydia.pintscher
> KDE e.V. Board of Directors
> http://kde.org - http://open-advice.org
regards, Jaroslaw Staniek
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kde-community