Telemetry Policy - Remaining Questions

Ben Cooksley bcooksley at kde.org
Tue Apr 3 08:17:23 UTC 2018


On Tue, Apr 3, 2018 at 11:20 AM, Jaroslaw Staniek <staniek at kde.org> wrote:
>
>
> On 2 April 2018 at 22:56, Lydia Pintscher <lydia at kde.org> wrote:
>>
>> Hey Jaroslaw :)
>>
>> On Mon, Apr 2, 2018 at 10:28 PM, Jaroslaw Staniek <staniek at kde.org> 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:
>> >
>> > https://community.kde.org/index.php?title=Policies/Telemetry_Policy&oldid=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.
>> >
>> >
>> https://community.kde.org/Talk:Policies/Telemetry_Policy#
>>
>> Thank you! Volker is probably best equipped to answer these.
>>
>> > That said: I will nod to the concept of "Minimalism", it is all classic
>> > property of telemetry. I think I've seen them in other projects too.
>> > I'd just say, let's not make all this more limited than anyone wants it
>> > to
>> > be.
>>
>> Where is it too limited? Please keep in mind that we've set
>> privacy as
>> a core part of our vision and the current goals.
>
>
> Lydia,

Hi Jaroslaw,

> It's a core part but still a part and can't contradict, say, with the
> Freedom part.
>
> Please see the list of limitations:
>  https://community.kde.org/Talk:Policies/Telemetry_Policy#
> (in my opinion that's not a "nice to haves" but requirements needed so we
> can even call the whole thing "telemetry")
>
> I am asking for an alternative approaches, Volker once mentioned there are
> some.
> We need them to we move forward.
>
> In the meantime my stack runs just well, people that use IDs are even given
> right to remove their data, something that's *not* going to be possible with
> the proposed vision. Someone would convince me otherwise.

Please don't drag our websites ability to have people login to them
into your argument here.
Cookies as used by websites are quite different to Telemetry on many points.

Regards,
Ben

>
> --
> regards, Jaroslaw Staniek
>
> KDE:
> : A world-wide network of software engineers, artists, writers, translators
> : and facilitators committed to Free Software development - http://kde.org
> KEXI:
> : A visual database apps builder - http://calligra.org/kexi
>   http://twitter.com/kexi_project https://facebook.com/kexi.project
> Qt Certified Specialist:
> : http://www.linkedin.com/in/jstaniek



More information about the kde-community mailing list