Received-SPF: pass
    (kde.org: 46.4.96.248 is authorized to use 'kde-community-bounces@kde.org' in 'mfrom' identity (mechanism 'mx' matched))
    receiver=mx1.messagingengine.com;
    identity=mailfrom;
    envelope-from="kde-community-bounces@kde.org";
    helo=postbox.kde.org;
    client-ip=46.4.96.248
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=2607:f8b0:4001:c0b::22f; helo=mail-it0-x22f.google.com;
 envelope-from=valorie.zimmerman@gmail.com; receiver=kde-community@kde.org 
MIME-Version: 1.0
In-Reply-To: <2990543.KVDkBByYO0@minixfox>
References: <2048912.XfIJe3ZSdj@vkpc5> <2990543.KVDkBByYO0@minixfox>
From: Valorie Zimmerman <valorie.zimmerman@gmail.com>
Date: Wed, 16 Aug 2017 00:33:02 -0700
Message-ID: <CACpu024EH1OeDqwL94QK33eq4sCGjKjwedcQDR_PWjprBevzfg@mail.gmail.com>
Subject: Re: Telemetry Policy
To: informing about and discussing non-technical community topics
 <kde-community@kde.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: list
Reply-To: informing about and discussing non-technical community topics
 <kde-community@kde.org>
Errors-To: kde-community-bounces@kde.org
Sender: "kde-community" <kde-community-bounces@kde.org>

Hi all, Mozilla has done a lot of work on telemetry, and we might be
able to use some of their findings. On this page:
https://wiki.mozilla.org/Firefox/Data_Collection they break down the
data they might possibly collect into four buckets - technical (such
as crashes), user interaction, web activity, and sensitive (personal
data).

This bit might be relevant to our discussion: "Categories 1 & 2
(Technical & Interaction data)
Pre-Release & Release: Data may default on, provided the data is
exclusively in these categories (it cannot be in any other category).
In Release, an opt-out must be available for most types of Technical
and Interaction data. "

I think the entire page might be enlightening to this discussion. I
believe our analysis of needs should be more fine-grained, and that
some parts of what we need can be "default on" especially for
pre-release testing. For releases, we can provide an opt-out.

Other more sensitive data will need to be opt-in. I think it's a
mistake to treat all the data we might want all in the same way.

Valorie


On Sun, Aug 13, 2017 at 3:18 AM, Christian Loosli
<christian.loosli@fuchsnet.ch> wrote:
> Hi,
>
> thank you very much for this work, sounds great!
>
> Only point I have: maybe make sure that the opt-in / default settings are not
> only mandatory for application developers, but also for packagers /
> distributions.
>
> Some distributions have rather questionable views on privacy and by default
> sent information to third parties, so I would feel much more safe if they
> weren't allowed (in theory) to flick the switch in their package by default to
> "on" either.
>
> Kind regards,
>
> Christian


-- 
http://about.me/valoriez