Telemetry Policy

into proper wording below. What do you think? Did I miss anything? Regards, Volker # Telemetry Policy Draft Application telemetry data can be a valuable tool for tailoring our products to the needs of our users. The following rules define how KDE collects and uses such application telemetry dat

Re: Telemetry Policy

he user can actually review what data has been send? And a log on when it was send. This way an user can actually audit the data if she so desires. This would improve the accountability on the promises you give in the Telemetry Policy Draft. Maybe the user would never look at the data, but know

Re: Telemetry Policy

made available under a CC license (CC0?) * maybe allow the user to delete the dataset again (difficult as that conflicts with making the data public and would require authentication which is the opposite to anonymity). Cheers Martin Regards, Volker # Telemetry Policy Draft Application telemetry

Re: Telemetry Policy

Hi Volker et al. On Sonntag, 13. August 2017 11:47:28 CEST Volker Krause wrote: > Hi, > > during the KUserFeedback BoF at Akademy there was quite some interest in > collecting telemetry data in KDE applications. But before actually > implementing that we agreed to define the rules under which we

Re: Telemetry Policy

On Sunday 13 August 2017 12:56:27 Martin Flöser wrote: > Am 2017-08-13 11:47, schrieb Volker Krause: > > Hi, > > > > during the KUserFeedback BoF at Akademy there was quite some > > interest > > in > > collecting telemetry data in KDE applications. But before actually > > implementing that we agre

Re: Telemetry Policy

Hi all, While I do see the point behind 'off-by-default', I think it will ruin the purpose since nobody will turn it on. I'd propose having it on by default (at least) for pre-releases. Cheers, Ivan

Re: Telemetry Policy

On 08/14/2017 05:30 PM, Ivan Čukić wrote: > Hi all, > > While I do see the point behind 'off-by-default', I think it will ruin > the purpose since nobody will turn it on. > > I'd propose having it on by default (at least) for pre-releases. I'm not convinced. KDE publically runs on a platform o

Re: Telemetry Policy

Hi, > On 08/14/2017 05:30 PM, Ivan Čukić wrote: >> Hi all, >> >> While I do see the point behind 'off-by-default', I think it will ruin >> the purpose since nobody will turn it on. >> >> I'd propose having it on by default (at least) for pre-releases. > > I'm not convinced. KDE publically runs

Re: Telemetry Policy

Am Montag, 14. August 2017, 10:57:10 CEST schrieb Dr.-Ing. Christoph Cullmann: > Hi, Morning > > On 08/14/2017 05:30 PM, Ivan Čukić wrote: > >> Hi all, > >> > >> While I do see the point behind 'off-by-default', I think it will ruin > >> the purpose since nobody will turn it on. > >> > >> I'd p

Re: Telemetry Policy

signing people some kind of unique identifier (which defeats the anonymity point) wouldn't allow them to delete just their own data. People would need to accept that whatever information is submitted is not removable. > > Cheers > Martin Cheers, Ben > > >> >> Regards,

Re: Telemetry Policy

olicy too much to what happens to be implemented right now. The policy doesn't state anything about "encouraging" to opt-in at this point. We probably want to add something about not "forcing" opt-in by for example not offering certain features only if telemetry in enabled.

Re: Telemetry Policy

if telemetry in enabled. Beyond > that it's mainly a marketing thing that doesn't need to be regulated by the > telemetry policy IMHO. > > The current implementation offers an encouragement system where it displays > a passive popup after a certain time of using

Re: Telemetry Policy

e would want to > do that. I've tried to put the input we collected during Akademy into proper > wording below. What do you think? Did I miss anything? > > Regards, > Volker > > > # Telemetry Policy Draft > > Application telemetry data can be a valuable tool for

Re: Telemetry Policy

I agree on the proposed wording changes, so focusing on your technical points below. On Monday, 14 August 2017 11:53:17 CEST Ben Cooksley wrote: > I've got two technical notes here: > > 1) All products should fetch details on where to submit telemetry data > from an online configuration file sim

Re: Telemetry Policy

le and return that to the client. The client collects those and can use them as part of a deletion request. However, this does only work as long as we have full control over the data, we can't recall data that has already been extracted from our systems. So I think this conflicts wit

Re: Telemetry Policy

Hello Volker, First of all thanks for working on this topic, I've some comments I would like to add. On Sun, Aug 13, 2017 at 11:47:28AM +0200, Volker Krause wrote: > ## Control > > We give the user full control over what data they want to share with KDE. In > particular: > - application telemet

Re: Telemetry Policy

Hi, On Montag, 14. August 2017 17:46:12 CEST Bhushan Shah wrote: > Hello Volker, > > First of all thanks for working on this topic, I've some comments I > would like to add. > > On Sun, Aug 13, 2017 at 11:47:28AM +0200, Volker Krause wrote: > > ## Control > > > > We give the user full control

Re: Telemetry Policy

Hello Thomas, On Mon, Aug 14, 2017 at 02:32:46PM +0200, Thomas Baumgart wrote: > What does keeping the local data in encrypted form help here? The application > (KUserFeedback function?) must be able to display the transferred data to the > user upon his request, so it needs to decrypt it. The k

Re: Telemetry Policy

key if you have to assume local file system access of an untrusted process? I can only think of one safe place that's not either compromised or would violate the rules of the telemetry policy: the user's head. But I doubt we'd want to bother them with a password for the telemetry d

Re: Telemetry Policy

ot;. So if it's technically possible it would be nice to have. Cheers Martin Regards, Volker > # Telemetry Policy Draft > > Application telemetry data can be a valuable tool for tailoring our > products > to the needs of our users. The following rules define how KDE collects &

Re: Telemetry Policy

On Monday, 14 August 2017 14:16:12 CEST Bhushan Shah wrote: > Hello Volker, > > First of all thanks for working on this topic, I've some comments I > would like to add. > > On Sun, Aug 13, 2017 at 11:47:28AM +0200, Volker Krause wrote: > > ## Control > > > > We give the user full control over wh

Re: Telemetry Policy

ld want to > do that. I've tried to put the input we collected during Akademy into > proper wording below. What do you think? Did I miss anything? > > Regards, > Volker > > > # Telemetry Policy Draft Added to the wiki, so we have version control: https://commu

Re: Telemetry Policy

tions. But > > before actually implementing that we agreed to define the rules > > under which we would want to do that. I've tried to put the input > > we collected during Akademy into proper wording below. What do you > > think? Did I miss anything? > >

Re: Telemetry Policy

On Sonntag, 13. August 2017 11:47:28 CEST Volker Krause wrote: > ## Minimalism > > We only track the bare minimum of data necessary to answer specific > questions, we do not collect data preemptively or for exploratory research. > In particular, this means: > - collected data must have a clear p

Re: Telemetry Policy

On Monday 14 August 2017 22:26:36 Thomas Pfeiffer wrote: > On Sonntag, 13. August 2017 11:47:28 CEST Volker Krause wrote: > > ## Minimalism > > > > We only track the bare minimum of data necessary to answer specific > > questions, we do not collect data preemptively or for exploratory > > research

Re: Telemetry Policy

On Monday 14 August 2017 19:28:06 Volker Krause wrote: > On Monday, 14 August 2017 14:16:12 CEST Bhushan Shah wrote: > > Can we have policy on how long we can store data? It's just random > > idea but I think it makes sense to tell users that after X period > > of time your data will be invalidated

Re: Telemetry Policy

into proper wording below. What do you >> > think? Did I miss anything? >> > >> > Regards, >> > Volker >> > >> > >> > # Telemetry Policy Draft >> > >> > Application telemetry data can be a valuable tool for tailoring our &

Re: Telemetry Policy

On Sunday 13 August 2017 11:47:28 Volker Krause wrote: > Hi, > > during the KUserFeedback BoF at Akademy there was quite some interest > in collecting telemetry data in KDE applications. But before actually > implementing that we agreed to define the rules under which we would > want to do that. I

Re: Telemetry Policy

On Monday, 14 August 2017 22:40:28 CEST Ingo Klöcker wrote: > On Monday 14 August 2017 19:28:06 Volker Krause wrote: > > On Monday, 14 August 2017 14:16:12 CEST Bhushan Shah wrote: > > > Can we have policy on how long we can store data? It's just random > > > idea but I think it makes sense to tell

Re: Telemetry Policy

On Monday, 14 August 2017 22:26:36 CEST Thomas Pfeiffer wrote: > On Sonntag, 13. August 2017 11:47:28 CEST Volker Krause wrote: > > ## Minimalism > > > > We only track the bare minimum of data necessary to answer specific > > questions, we do not collect data preemptively or for exploratory > > re

Re: Telemetry Policy

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

Re: Telemetry Policy

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 activit

Re: Telemetry Policy

On Mon, Aug 14, 2017 at 11:40 PM, Volker Krause wrote: > I agree on the proposed wording changes, so focusing on your technical points > below. > > On Monday, 14 August 2017 11:53:17 CEST Ben Cooksley wrote: >> I've got two technical notes here: >> >> 1) All products should fetch details on where

Re: Telemetry Policy

On Wednesday, 16 August 2017 10:21:11 CEST Ben Cooksley wrote: > On Mon, Aug 14, 2017 at 11:40 PM, Volker Krause wrote: > > I agree on the proposed wording changes, so focusing on your technical > > points below. > > > > On Monday, 14 August 2017 11:53:17 CEST Ben Cooksley wrote: > >> I've got tw

Re: Telemetry Policy

Hi, before this gets completely out of hand: The cited German data protection regulations are often misunderstood, even by people that pose as experts. They are also often (mis-)used as killer arguments to support political or personal opinions. If we start collecting telemetry data, we should

Re: Telemetry Policy

On Sunday, 13 August 2017 12:18:16 CEST Christian Loosli 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. > >

Re: Telemetry Policy

On Wed, Aug 16, 2017 at 9:06 PM, Volker Krause wrote: > On Wednesday, 16 August 2017 10:21:11 CEST Ben Cooksley wrote: >> On Mon, Aug 14, 2017 at 11:40 PM, Volker Krause wrote: >> > I agree on the proposed wording changes, so focusing on your technical >> > points below. >> > >> > On Monday, 14 A

Re: Telemetry Policy

On Wednesday, 16 August 2017 09:33:02 CEST Valorie Zimmerman wrote: > 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 in

Re: Telemetry Policy

Am Mittwoch, 16. August 2017, 00:33:02 CEST schrieb Valorie Zimmerman: > 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.

Re: Telemetry Policy

Am Mittwoch, 16. August 2017, 11:46:12 CEST schrieb Volker Krause: > Valid point, I've added a statement to the policy asking distributors of our > products to respect the rules too. Thank you very much :) > I don't think we can make this a hard requirement (as in: you lose the right > to distr

Re: Telemetry Policy

On 16 August 2017 at 14:13, Volker Krause wrote: > On Wednesday, 16 August 2017 09:33:02 CEST Valorie Zimmerman wrote: > > 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_Collectio

Re: Telemetry Policy

On Wed, 16 Aug 2017, Volker Krause wrote: > Seeing yesterday's blog from the Krita team (https://akapust1n.github.io/ > 2017-08-15-sixth-blog-gsoc-2017/), I'd particularly be interested in their > view on this. I've pointed alexey at this thread, but there's a huge language barrier: he basically

Re: Telemetry Policy

On Wednesday, 16 August 2017 15:23:07 CEST Jaroslaw Staniek wrote: > On 16 August 2017 at 14:13, Volker Krause wrote: > > On Wednesday, 16 August 2017 09:33:02 CEST Valorie Zimmerman wrote: > > > Hi all, Mozilla has done a lot of work on telemetry, and we might be > > > able to use some of their f

Re: Telemetry Policy

On Wed, 16 Aug 2017, Volker Krause wrote: > The policy we are discussing here is (and is supposed to be) independent of > the implementation. And that's not just theoretical, Kexi is one prominent > case for an alternative implementation, and the Krita GSoC also seems to > contain some alternat

Re: Telemetry Policy

On Wednesday, 16 August 2017 11:31:31 CEST Mirko Boehm - KDE wrote: > before this gets completely out of hand: The cited German data protection > regulations are often misunderstood, even by people that pose as experts. > They are also often (mis-)used as killer arguments to support political or >

Re: Telemetry Policy

On 16 August 2017 at 18:56, Volker Krause wrote: > On Wednesday, 16 August 2017 15:23:07 CEST Jaroslaw Staniek wrote: > > On 16 August 2017 at 14:13, Volker Krause wrote: > > > On Wednesday, 16 August 2017 09:33:02 CEST Valorie Zimmerman wrote: > > > > Hi all, Mozilla has done a lot of work on t

Re: Telemetry Policy

On Mittwoch, 16. August 2017 09:33:02 CEST Valorie Zimmerman wrote: > 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 in

Re: Telemetry Policy

On Wednesday, 16 August 2017 20:35:59 CEST Jaroslaw Staniek wrote: > On 16 August 2017 at 18:56, Volker Krause wrote: > > On Wednesday, 16 August 2017 15:23:07 CEST Jaroslaw Staniek wrote: > > > On 16 August 2017 at 14:13, Volker Krause wrote: [...] > > > In addition maybe distributors can someti

Re: Telemetry Policy

Hi, > On 17. Aug 2017, at 01:46, Thomas Pfeiffer wrote: > > Hi Valorie, > Even if opt-out for some data is legally and even morally fine, it does not > align with the values we communicate to our users: > Unlike Mozilla's Mission, our Vision mentions privacy explicitly, and we're > striving to m

Re: Telemetry Policy

> On 17. Aug 2017, at 17:38, Mirko Boehm - KDE wrote: > > Hi, > >> On 17. Aug 2017, at 01:46, Thomas Pfeiffer > > wrote: >> >> Hi Valorie, >> Even if opt-out for some data is legally and even morally fine, it does not >> align with the values we communicate to

Re: Telemetry Policy

On 17 August 2017 at 18:20, Thomas Pfeiffer wrote: > > On 17. Aug 2017, at 17:38, Mirko Boehm - KDE wrote: > > Hi, > > On 17. Aug 2017, at 01:46, Thomas Pfeiffer > wrote: > > Hi Valorie, > Even if opt-out for some data is legally and even morally fine, it does not > > align with the values we c

Re: Telemetry Policy

On 17 August 2017 at 16:19, Volker Krause wrote: > On Wednesday, 16 August 2017 20:35:59 CEST Jaroslaw Staniek wrote: > > On 16 August 2017 at 18:56, Volker Krause wrote: > > > On Wednesday, 16 August 2017 15:23:07 CEST Jaroslaw Staniek wrote: > > > > On 16 August 2017 at 14:13, Volker Krause w

Re: Telemetry Policy

Enviado desde mi iPhone >> El 16 ago 2017, a las 20:46, Thomas Pfeiffer >> escribió: >> >> On Mittwoch, 16. August 2017 09:33:02 CEST Valorie Zimmerman wrote: >> 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://wi

Re: Telemetry Policy

On Friday, 18 August 2017 11:23:49 CEST Jaroslaw Staniek wrote: > On 17 August 2017 at 16:19, Volker Krause wrote: > > On Wednesday, 16 August 2017 20:35:59 CEST Jaroslaw Staniek wrote: > > > On 16 August 2017 at 18:56, Volker Krause wrote: > > > > On Wednesday, 16 August 2017 15:23:07 CEST Jaros

Re: Telemetry Policy

On Saturday, 19 August 2017 05:37:58 CEST Nicolás Alvarez wrote: > Enviado desde mi iPhone > >> El 16 ago 2017, a las 20:46, Thomas Pfeiffer > >> escribió: > >> > >> On Mittwoch, 16. August 2017 09:33:02 CEST Valorie Zimmerman wrote: > >> Hi all, Mozilla has done a lot of work on telemetry, and w

Re: Telemetry Policy

​​ On 19 August 2017 at 11:39, Volker Krause wrote: > On Friday, 18 August 2017 11:23:49 CEST Jaroslaw Staniek wrote: > > On 17 August 2017 at 16:19, Volker Krause wrote: > > > On Wednesday, 16 August 2017 20:35:59 CEST Jaroslaw Staniek wrote: > > > > On 16 August 2017 at 18:56, Volker Krause w

Re: Telemetry Policy

On Sunday, 20 August 2017 22:29:28 CEST Jaroslaw Staniek wrote: > On 19 August 2017 at 11:39, Volker Krause wrote: > > On Friday, 18 August 2017 11:23:49 CEST Jaroslaw Staniek wrote: > > > On 17 August 2017 at 16:19, Volker Krause wrote: > > > > On Wednesday, 16 August 2017 20:35:59 CEST Jaroslaw

Re: Telemetry Policy

On Saturday 19 August 2017 12:02:03 Volker Krause wrote: > Good point, I clarified the intended meaning of "opt-in" in the wiki, that > is: off by default and only activated by explicit action of the user > (inaction is not good enough). Curiously, there's a lot of "

Re: Telemetry Policy

t; (inaction is not good enough). > > Curiously, there's a lot of "telemetry policy" news items popping up this > week, for instance: > > Mozilla ponders making telemetry opt-out, 'cos hardly anyone opted in > > (that's on the Register) and there we

Re: Telemetry Policy

> El 24 ago 2017, a las 07:41, Jaroslaw Staniek escribió: > >> On 24 August 2017 at 11:10, Adriaan de Groot wrote: >> >> Curiously, there's a lot of "telemetry policy" news items popping up this >> week, for instance: >> >>Moz

Re: Telemetry Policy

On 24 August 2017 at 16:54, Nicolás Alvarez wrote: > >> El 24 ago 2017, a las 07:41, Jaroslaw Staniek escribió: >> >>> On 24 August 2017 at 11:10, Adriaan de Groot wrote: >>> >>> Curiously, there's a lot of "telemetry polic

Re: Telemetry Policy

On Sun, 13 Aug 2017, Volker Krause wrote: > # Telemetry Policy Draft Do we already have a wiki page I can link to? I want to publish Alexey's experimental build today, and that needs to be announced pretty carefully. -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: Telemetry Policy

On Friday, 25 August 2017 10:11:09 CEST Boudewijn Rempt wrote: > On Sun, 13 Aug 2017, Volker Krause wrote: > > # Telemetry Policy Draft > > Do we already have a wiki page I can link to? I want to publish > Alexey's experimental build today, and that needs to be announced &

Telemetry Policy - Remaining Questions

Hi, as not everyone follows long threads, let's start again for the remaining issues. https://community.kde.org/Policies/Telemetry_Policy The following questions were left unanswered in the previous thread (see there for the full arguments if needed): (1) Should we allow opt-in tracking of un

Re: Telemetry Policy - Remaining Questions

On Wednesday, September 13, 2017 6:20:57 PM EDT Volker Krause wrote: > as not everyone follows long threads, let's start again for the remaining > issues. Thanks for pulling the threads back together again. > (1) Should we allow opt-in tracking of unique identifiers? > > This was requested by Ja

Re: Telemetry Policy - Remaining Questions

2017-09-13 19:20 GMT-03:00 Volker Krause : > (1) Should we allow opt-in tracking of unique identifiers? > > This was requested by Jaroslaw, as Kexi has this right now and the policy as > written right now would thus conflict with it. My view is that we need opt-out telemetry with unique identifier

Re: Telemetry Policy - Remaining Questions

On Thursday, 14 September 2017 09:02:07 CEST Adriaan de Groot wrote: > On Wednesday, September 13, 2017 6:20:57 PM EDT Volker Krause wrote: > > as not everyone follows long threads, let's start again for the remaining > > issues. > > Thanks for pulling the threads back together again. > > > (1) S

Re: Telemetry Policy - Remaining Questions

El dijous, 14 de setembre de 2017, a les 0:20:57 CEST, Volker Krause va escriure: > Hi, > > as not everyone follows long threads, let's start again for the remaining > issues. > > https://community.kde.org/Policies/Telemetry_Policy > > The following questions were left unanswered in the previou

Re: Telemetry Policy - Remaining Questions

On Thursday, 14 September 2017 20:56:49 CEST Albert Astals Cid wrote: > El dijous, 14 de setembre de 2017, a les 0:20:57 CEST, Volker Krause va > escriure: > > (1) Should we allow opt-in tracking of unique identifiers? > > > > This was requested by Jaroslaw, as Kexi has this right now and the pol

Re: Telemetry Policy - Remaining Questions

2017-09-14 15:56 GMT-03:00 Albert Astals Cid : > El dijous, 14 de setembre de 2017, a les 0:20:57 CEST, Volker Krause va > escriure: >> The following questions were left unanswered in the previous thread (see >> there for the full arguments if needed): >> >> (1) Should we allow opt-in tracking of u

Re: Telemetry Policy - Remaining Questions

On Friday, 15 September 2017 05:23:44 CEST Nicolás Alvarez wrote: > 2017-09-14 15:56 GMT-03:00 Albert Astals Cid : > > El dijous, 14 de setembre de 2017, a les 0:20:57 CEST, Volker Krause va > > > > escriure: > >> The following questions were left unanswered in the previous thread (see > >> there

Re: Telemetry Policy - Remaining Questions

2017-09-15 4:27 GMT-03:00 Volker Krause : > On Friday, 15 September 2017 05:23:44 CEST Nicolás Alvarez wrote: >> From Mozilla documentation: "So when you say '63% of beta 53 has >> Firefox set as its default browser', make sure you specify it is 63% >> of *pings*, since it is only around 46% of cli

Re: Telemetry Policy - Remaining Questions

On Saturday, 16 September 2017 07:54:48 CEST Nicolás Alvarez wrote: > 2017-09-15 4:27 GMT-03:00 Volker Krause : > > On Friday, 15 September 2017 05:23:44 CEST Nicolás Alvarez wrote: > >> From Mozilla documentation: "So when you say '63% of beta 53 has > >> Firefox set as its default browser', make

Re: Telemetry Policy - Remaining Questions

Let's try to finally get this finished :) The only remaining blocker is the unique identification used by Kexi. There was some discussion about this around QtWS, and it seemed like there was consensus on having a strong policy on this topic would be a good thing for KDE, as opposed to e.g. turn

Re: Telemetry Policy - Remaining Questions

On 30 October 2017 at 09:56, Volker Krause wrote: > Let's try to finally get this finished :) > > The only remaining blocker is the unique identification used by Kexi. There > was > some discussion about this around QtWS, and it seemed like there was consensus > on having a strong policy on this

Re: Telemetry Policy - Remaining Questions

El dilluns, 30 d’octubre de 2017, a les 9:56:52 CET, Volker Krause va escriure: > Let's try to finally get this finished :) > > The only remaining blocker is the unique identification used by Kexi. There > was some discussion about this around QtWS, and it seemed like there was > consensus on hav

Re: Telemetry Policy - Remaining Questions

On Monday, 30 October 2017 21:24:59 CET Albert Astals Cid wrote: > El dilluns, 30 d’octubre de 2017, a les 9:56:52 CET, Volker Krause va > > escriure: > > Let's try to finally get this finished :) > > > > The only remaining blocker is the unique identification used by Kexi. > > There > > was some

Re: Telemetry Policy - Remaining Questions

On Monday, 30 October 2017 11:27:58 CET Jaroslaw Staniek wrote: > On 30 October 2017 at 09:56, Volker Krause wrote: > > Let's try to finally get this finished :) > > > > The only remaining blocker is the unique identification used by Kexi. > > There was some discussion about this around QtWS, and

Re: Telemetry Policy - Remaining Questions

on the exception, not the rule. I'm thinking along the lines of require code released by KDE to adopt the policy and even add it to the manifesto as requirement to make it easier to enforce. Kexi can always make it opt-in, and could be given some time to do so before we officially adopt and require this telemetry policy. Jaroslaw, would that work for you? -- sebas http://www.kde.org | http://vizZzion.org

Re: Telemetry Policy - Remaining Questions

rd parties?) because... please read below: > I'm thinking along the lines of require code released by KDE to adopt > the policy and even add it to the manifesto as requirement to make it > easier to enforce. Kexi can always make it opt-in, and could be given > some time to do so b

Re: Telemetry Policy - Remaining Questions

27;m thinking along the lines of require code released by KDE to adopt > the policy and even add it to the manifesto as requirement to make it > easier to enforce. With respect to T7050 I agree with this, although we'd probably need a broader set of privacy-related policies for that, t

Re: Telemetry Policy - Remaining Questions

Hey folks :) We really need to wrap this up now. We need the data and we need the policy in place. It's holding us back from learning more about our users and making our software better. That's not good. On Sat, Nov 11, 2017 at 12:47 PM, Volker Krause wrote: > So, I see the following possible wa

Re: Telemetry Policy - Remaining Questions

On 1 April 2018 at 15:41, Lydia Pintscher wrote: > Hey folks :) > > We really need to wrap this up now. > ​​ > We need the data and we need the > policy in place. It's holding us back from learning more about our > users and making our software better. That's not good. > > On Sat, Nov 11, 2017 at

Re: Telemetry Policy - Remaining Questions

Hey Jaroslaw :) On Mon, Apr 2, 2018 at 10:28 PM, Jaroslaw Staniek 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, n

Re: Telemetry Policy - Remaining Questions

On 2 April 2018 at 22:56, Lydia Pintscher wrote: > Hey Jaroslaw :) > > On Mon, Apr 2, 2018 at 10:28 PM, Jaroslaw Staniek 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 giv

Re: Telemetry Policy - Remaining Questions

On Tue, Apr 3, 2018 at 11:20 AM, Jaroslaw Staniek wrote: > > > On 2 April 2018 at 22:56, Lydia Pintscher wrote: >> >> Hey Jaroslaw :) >> >> On Mon, Apr 2, 2018 at 10:28 PM, Jaroslaw Staniek wrote: >> > Thanks for reminding me Lydia >> > >> > I've not forgotten this. While there's progress I do s

Re: Telemetry Policy - Remaining Questions

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 wrote: > > Thanks for reminding me Lydia > > > > I've not forgotten this. While there's progress I do still see this a

Re: Telemetry Policy - Remaining Questions

​​ On 3 April 2018 at 10:17, Ben Cooksley wrote: > On Tue, Apr 3, 2018 at 11:20 AM, Jaroslaw Staniek wrote: > > > > > > On 2 April 2018 at 22:56, Lydia Pintscher wrote: > >> > >> Hey Jaroslaw :) > >> > >> On Mon, Apr 2, 2018 at 10:28 PM, Jaroslaw Staniek > wrote: > >> > Thanks for reminding

Re: Telemetry Policy - Remaining Questions

On 3 April 2018 at 10:42, Volker Krause wrote: > 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 > wrote: > > > Thanks for reminding me Lydia > > > > > > I'v

Re: Telemetry Policy - Remaining Questions

On Tuesday, 3 April 2018 18:16:10 CEST Jaroslaw Staniek wrote: > On 3 April 2018 at 10:42, Volker Krause wrote: > > > > https://community.kde.org/Talk:Policies/Telemetry_Policy# > > > > > > Thank you! Volker is probably best equipped to answer these. > > > > I've commented on all points on the t

Re: Telemetry Policy - Remaining Questions

On Tue, Apr 3, 2018 at 8:57 PM, Jaroslaw Staniek wrote: > > > On 3 April 2018 at 10:17, Ben Cooksley wrote: >> >> On Tue, Apr 3, 2018 at 11:20 AM, Jaroslaw Staniek wrote: >> > >> > >> > On 2 April 2018 at 22:56, Lydia Pintscher wrote: >> >> >> >> Hey Jaroslaw :) >> >> >> >> On Mon, Apr 2, 2018

Re: Telemetry Policy - Remaining Questions

On 4 April 2018 at 12:37, Ben Cooksley wrote: > On Tue, Apr 3, 2018 at 8:57 PM, Jaroslaw Staniek wrote: > > > > > > On 3 April 2018 at 10:17, Ben Cooksley wrote: > >> > >> On Tue, Apr 3, 2018 at 11:20 AM, Jaroslaw Staniek > wrote: > >> > > >> > > >> > On 2 April 2018 at 22:56, Lydia Pintscher

Re: Telemetry Policy - Remaining Questions

Hey folks, Jaroslaw: * 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 personall

Re: Telemetry Policy - Remaining Questions

On 30 April 2018 at 22:08, Lydia Pintscher wrote: > Hey folks, > > Jaroslaw: > * 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

Re: Telemetry Policy - Remaining Questions

On Mon, Apr 30, 2018 at 10:41 PM Jaroslaw Staniek wrote: > Hello > Now we can assume that solution to non-unique identification Volker explained in acceptable equivalent of random identifiers so KEXI does not need exception. > Thanks for patience! > I understand KEXI has time until the next relea

Re: Telemetry Policy - Remaining Questions

On 30 April 2018 at 22:54, Lydia Pintscher wrote: > On Mon, Apr 30, 2018 at 10:41 PM Jaroslaw Staniek wrote: > > Hello > > Now we can assume that solution to non-unique identification Volker > explained in acceptable equivalent of random identifiers so KEXI does not > need exception. > > Thanks