On 31 October 2017 at 11:56, Sebastian Kügler <[email protected]> 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 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. turning this into just recommendations, or >> > > opening >> > > it up to unique identification. The suggested solution for Kexi >> > > was to add >> > > a special exception for it to the "These rules apply to all >> > > products released by KDE." statement of the policy. >> >> > I'm confused, is that a workaround so that it doesn't apply to Kexi >> > by implying Kexi isn't released by KDE? >> >> That sounds a bit convoluted to me, I was more thinking about making >> it a direct exception to the policy, e.g. like this: >> >> "These rules apply to all products released by KDE (with the >> exception of Kexi, which uses a telemetry system predating this >> policy)." > > This will make the communication downright awful, as people will > concentrate on the exception, not the rule. >
I am sure energy would be concentrated on exception and nonconstructive activities (from 3rd 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 before we officially adopt and require this > telemetry policy. > Jaroslaw, would that work for you? because... one thing is apparently missed even in this internal thread: IIRC Kexi apps have never offered opt-out policy even for anonymous telemetry. I blogged about that as soon as the feature landed [1]. Users pick level of involvement, zero by default, and telemetry is presented as a way for involvement in the project not as a threat. [1] https://blogs.kde.org/2013/12/09/usage-stats -- regards, Jaroslaw Staniek KDE: : A world-wide network of software engineers, artists, writers, translators : and facilitators committed to Free Software development - http://kde.org Calligra Suite: : A graphic art and office suite - http://calligra.org Kexi: : A visual database apps builder - http://calligra.org/kexi Qt Certified Specialist: : http://www.linkedin.com/in/jstaniek
