Re: Conservative proposal: let's work with Kiwi IRC

On August 16, 2017 6:58:35 PM GMT+09:00, Ilmari Lauhakangas wrote: >I want to note that I was intrigued by Eike's mail about a possible Qt >Quick -based Konversation reboot. I suggested I could try and gather >funding to get it to a releasable state, but he

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

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,

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 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

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

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

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: > >

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

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: [kde-community] Conservative proposal: let's work with Kiwi IRC

On 16.08.2017 14:56, Jonathan Riddell wrote: On Wed, Aug 16, 2017 at 12:58:35PM +0300, Ilmari Lauhakangas wrote: The work-in-progress Kiwi Next client can be tested like so: https://kiwiirc.com/nextclient/#irc://irc.freenode.net/kde You can add more channels separated with commas. Looks like

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

Re: [kde-community] Conservative proposal: let's work with Kiwi IRC

On Wed, Aug 16, 2017 at 12:58:35PM +0300, Ilmari Lauhakangas wrote: > The work-in-progress Kiwi Next client can be tested like so: > https://kiwiirc.com/nextclient/#irc://irc.freenode.net/kde > You can add more channels separated with commas. Looks like another IRC web client. It's just as full

Re: Conservative proposal: let's work with Kiwi IRC

On 16.08.2017 14:08, Christian Loosli wrote: I mostly agree, even though I am unsure of how certain things could be implemented, e.g. * Editing messages which IRC simply does not support. So my best guess would be that this only works for people using the Kiwi solution, or the IRC people

Re: Conservative proposal: let's work with Kiwi IRC

Hi, thanks for posting to the list! I mostly agree, even though I am unsure of how certain things could be implemented, e.g. > * Editing messages which IRC simply does not support. So my best guess would be that this only works for people using the Kiwi solution, or the IRC people will

Re: Proposal: Have the Community Set Ambitious Goals for Itself

On dinsdag 15 augustus 2017 00:47:15 CEST Lydia Pintscher wrote: > If I get at least two people to agree in this thread that they will > submit a goal I commit to making the process work according to the > proposed timeline. I'll do that. We probably should coordinate somehow which goals, so we

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 >> >

Conservative proposal: let's work with Kiwi IRC

Hello you radicals. I am a KDE user and contributor and a member of The Document Foundation. Jonathan already referred to my mail on the LibreOffice projects list, so I might as well branch out here. I've been working with Kiwi IRC's lead developer Darren for some weeks now. Today I showed

Re: Code signing certificate for KDE?

On Wed, 16 Aug 2017, Gilles Caulier wrote: > Hi, > > Same problem for digiKam Windows installer. > > But this question is not only about Windows, but MacOS PKG also need > to be signed. So the problem is more generic and a global solution > need to be found here for KDE applications packaged

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: Code signing certificate for KDE?

Hi, Same problem for digiKam Windows installer. But this question is not only about Windows, but MacOS PKG also need to be signed. So the problem is more generic and a global solution need to be found here for KDE applications packaged for windows and MacOS. Note : in the future, to improve

Re: Collecting requirements for a KDE-wide instant messaging solution (was: Re: radical proposal: move IRC to Rocket.Chat)

Hi Thomas, thanks for this issue forward with a rather constructive approach! > On 16. Aug 2017, at 03:20, Thomas Pfeiffer wrote: > > I have now cleaned up https://notes.kde.org/p/KDE_IM_requirements > by removing >

Code signing certificate for KDE?

Here's yet another topic: for the past year, I've been signing Krita for Windows with a certificate from certum.eu. These certificates are personal, so krita gets signed by "open source developer boudewijn rempt". That's not ideal, and besides, there are other projects publishing binaries for

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 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

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

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