Telemetry Policy - Remaining Questions

[Jaroslaw Staniek]

On 1 April 2018 at 15:41, Lydia Pintscher <lydia at kde.org> 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 12:47 PM, Volker Krause <vkrause at kde.org> wrote:
> > So, I see the following possible ways forward:
> > (1) We accept the policy in its current spirit, and Kexi complies with
> it (if
> > necessary after some transition period).
>
> This would be the ideal way forward and the right thing to do.
>
> > (2) We accept the policy in its current spirit, and Kexi is exempt from
> it.
>
> As sebas said this is bad communication-wise. But if Kexi can't or
> doesn't want to comply that's the next best option.
>
> > (3) We make the policy opt-in, ie. using it merely as an extra quality
> > criteria for the applications wanting to follow it.
>
> I don't believe this is an option that's in line with our vision.
>
> > (4) We give up on the idea of regulating telemetry, rolling back on the
> > decision from Akademy.
>
> I don't think that's an acceptable option either because we need to
> get a better understanding of how our software is used in order to
> make it better.
>
> Jaroslav: I think you need to make a choice now for Kexi. We can't let
> it sit and hope it goes away ;-)
>


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, not a core feature of any product.

Below I am referring to this version: https://community.
kde.org/index.php?title=Policies/Telemetry_Policy&oldid=78057

tl;dr: Why discussing: Any deep change and limitation to projects' freedom
needs to bring substantial benefits over drawbacks. Level of complexity of
the contract for a project or individual developer needs to be balanced by
real (not hypothetical) benefits.

I've studied the wiki page more in depth and I have these points where I'd
like to see improvement. This is based on my experience, not a list of
quick ideas.

https://community.kde.org/Talk:Policies/Telemetry_Policy#

That said: I will nod to the concept of "Minimalism", it is all classic
property of telemetry. I think I've seen them in other projects too.
I'd just say, let's not make all this more limited than anyone wants it to
be.

-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
KEXI:
: A visual database apps builder - http://calligra.org/kexi
  http://twitter.com/kexi_project https://facebook.com/kexi.project
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20180402/9c672449/attachment.htm>