Telemetry Policy - Remaining Questions

Volker Krause vkrause at
Tue Apr 3 08:42:31 UTC 2018

Thanks Lydia for getting this moving again!

On Monday, 2 April 2018 22:56:31 CEST Lydia Pintscher wrote:
> Hey Jaroslaw :)
> On Mon, Apr 2, 2018 at 10:28 PM, Jaroslaw Staniek <staniek at> wrote:
> > Thanks for reminding me Lydia
> > 
> > I've not forgotten this. While there's progress I do still see this as a
> > pilot stage and do not think we're in a hurry given telemetry is something
> > "extra" for a project development, not a core feature of any product.
> We are in a hurry now. We're waiting for projects to be able to start
> using it and get us valuable insights about how our software is used.
> We've been on it since last Akademy. Let's get it finished :)
> > Below I am referring to this version:
> >
> > 78057
> > 
> > tl;dr: Why discussing: Any deep change and limitation to projects' freedom
> > needs to bring substantial benefits over drawbacks. Level of complexity of
> > the contract for a project or individual developer needs to be balanced by
> > real (not hypothetical) benefits.
> The benefits here for KDE are:
> * we have a better understanding of our userbase leading hopefully to
> better software
> * we have a better understanding of our userbase leading hopefully to
> better marketing
> * we have a clear policy we can point our users to that explains how
> we are handling their data and that is in line with our vision/what we
> stand for.
> > I've studied the wiki page more in depth and I have these points where I'd
> > like to see improvement. This is based on my experience, not a list of
> > quick ideas.
> > 
> >
> Thank you! Volker is probably best equipped to answer these.

I've commented on all points on the talk page now I think.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the kde-community mailing list