Telemetry Policy

[Mario Fux]

Am Montag, 14. August 2017, 11:48:04 CEST schrieb Volker Krause:

Morning

[snip]

> > > At the moment, we can not even judge how much data we receive with that
> > > policy, we can still re discuss that if we really see we get not enough
> > > feedback to have usable data.
> > 
> > So general question: How do we communicate or offer to set it on?
> > First-run
> > dialog? Release notes?
> 
> Let's make sure to keep policy and current implementation separate to avoid
> confusion and to avoid tying the policy too much to what happens to be
> implemented right now.

Of course that makes sense.

> 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. 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 the application. It's
> intentionally not a first run dialog, that would generate a very bad first
> impression. But it's also intentionally a (recurring) in-app notification as
> I doubt we'd get much data if it's purely mentioned in the release notes,
> or the user just happens to find the option somewhere.

Thanks for this information regarding the current implementation.

> The participation ratio is one of the big unknowns so far, so this is an
> important aspect.

Of course but nonetheless thanks for your work on the KUserFeedback (soon-to-
be ;-) framework.

Mario