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

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

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

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

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

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

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

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,

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

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

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

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

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,

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

Re: Telemetry Policy - Remaining Questions

On Tuesday, 31 October 2017 11:56:23 CET Sebastian Kügler wrote: > On Tuesday, October 31, 2017 10:39:38 AM CET Volker Krause wrote: > > 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 > > > > > > >

Re: Telemetry Policy - Remaining Questions

On 31 October 2017 at 11:56, Sebastian Kügler wrote: > On Tuesday, October 31, 2017 10:39:38 AM CET Volker Krause wrote: >> 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 >> > > Let's

Re: Telemetry Policy - Remaining Questions

On Tuesday, October 31, 2017 10:39:38 AM CET Volker Krause wrote: > 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 > > > Let's try to finally get this finished > > > > > > The only remaining blocker

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

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

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

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

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.

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

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

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

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

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

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)

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

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

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