Hi,

Use of KUserFeedback is problematic due to its license. Adding 3rd party L/GPL 
components is something I do not want to do (already wrote "we", but let's use 
"I" instead to avoid need to define what is meant by we :) The reason for 
avoiding adding any 3rd party components with viral licenses is coming from the 
commercial licensee needs.

If KUserFeedback does what is needed from the discussed Qt add-on module, and 
the persons who wrote it are interested in contributing it to Qt, that could be 
one approach. 

That said, I have not looked into KUserFeedback myself beyond licensing.

Yours,

        Tuukka 

On 23/02/2018, 11.22, "Development on behalf of Volker Krause" 
<development-bounces+tuukka.turunen=qt...@qt-project.org on behalf of 
volker.kra...@kdab.com> wrote:

    Hi,
    
    as numerous people have asked me to comment on this by now, let me just do 
    that here publicly (representing KDE's KUserFeedback, not KDAB):
    
    Tino is well aware of KUserFeedback, we discussed that last year already in 
    detail. So it definitely was considered as a possible solution for this.
    I do not know why it was ultimately decided to implement a new framework, 
in 
    particular if that's due to conceptual or technical reasons, or licensing.
    
    
    With the KDAB hat back on, we do use KUserFeedback in GammaRay since mid 
last 
    year, and it has so far provided a few useful insights, in particular 
    regarding to what extend we still need to support ancient Qt versions. But 
as 
    with any data, it's not the ultimate answer to all questions, and you need 
to 
    be very careful how to interpret it obviously. We have so far not received 
any 
    negative feedback with e.g. privacy concerns, but the approach 
KUserFeedback 
    takes there by default (and that we followed in GammaRay) is intentionally 
    very restrained.
    
    Regards,
    Volker
    
    On Thursday, 22 February 2018 14:58:55 CET Tino Pyssysalo wrote:
    > Hi,
    > 
    > The idea is to develop a generic library/plugin, which anyone could use 
for
    > analytics. The backend can be any storage and The Qt Company does not
    > provide that.
     
    > We plan to use the same backend, which we already use in online installers
    > to collect statistics about installations. At least in case of Qt Creator,
    > the plan is to make some analysis results available for the community.
    > Obviously, we do not do that for our commercial tooling.
     
    > Analytics is opt-in and disabled by default in Qt Creator. We plan to ask
    > user in the installer, if the user wish to participate in Qt UX
    > improvement. If the answers is no, the analytics plugin is never 
installed.
    >  When the creator is started for the first time, it will show a dialog,
    > consisting a list of collected data items and an option to enable/disable
    > the plugin. There will be a new output pane, which shows collected data,
    > conversions methods, if any used, and transmitted data to the user.
     --
    > Tino
    > 
    > 
    > On 22/02/2018, 15.26, "Simon Hausmann"
    > <simon.hausm...@qt.io<mailto:simon.hausm...@qt.io>> wrote:
     
    > 
    > Hi,
    > 
    > 
    > 
    > Can you provide a bit more information about how this plugin / frontend 
fits
    > into the Qt project? Where is the collected data sent to and how is it
    > accessible to the community?
     
    > 
    > 
    > (-1 from me, as I think this needs to be clarified)
    > 
    > 
    > 
    > Simon
    > 
    > ________________________________
    > From: Development 
<development-bounces+simon.hausmann=qt...@qt-project.org>
    > on behalf of Tuukka Turunen <tuukka.turu...@qt.io>
     Sent: Thursday,
    > February 22, 2018 2:14:14 PM
    > To: Tino Pyssysalo; qt-crea...@qt-project.org; development@qt-project.org
    > Subject: Re: [Development] [Qt-creator] Requesting repository for 
telemetry
    > plugin in Qt Creator
     
    > 
    > 
    > 
    > Hi,
    > 
    > 
    > 
    > +1 for creating the repo, but what about qt/qtanalytics as a name? This 
item
    > could be useful also for other applications.
     
    > 
    > 
    > Yours,
    > 
    > 
    > 
    >                              Tuukka
    > 
    > 
    > 
    > From: Qt-creator <qt-creator-bounces+tuukka.turunen=qt...@qt-project.org> 
on
    > behalf of Tino Pyssysalo <tino.pyssys...@qt.io>
     Date: Thursday, 22
    > February 2018 at 13.04
    > To: "qt-crea...@qt-project.org" <qt-crea...@qt-project.org>
    > Subject: [Qt-creator] Requesting repository for telemetry plugin in Qt
    > Creator
     
    > 
    > 
    > Description:
    > 
    > 
    > 
    > Telemetry plugin (frontend) to collect usage data from Qt Creator to help
    > improving Qt, Qt features, and Qt tools.
     
    > Non-personal data items, such as duration the user spent in design mode,
    > will be collected in a way, which is completely transparent to the user.
     
    > 
    > 
    > Responsible: Tino Pyssysalo
    > 
    > 
    > 
    > Repository: qt-creator/plugin-telemetry
    > 
    > 
    > 
    > 
    > 
    > ---
    > 
    > Tino Pyssysalo
    > 
    > Senior Manager
    > 
    > 
    > 
    > The Qt Company
    > 
    > Hämeenkatu 14 C 25
    > 
    > 33100 Tampere, Finland
    > 
    > tino.pyssys...@qt.io<mailto:tino.pyssys...@qt.io>
    > 
    > +358 40 8615475
    > 
    > http://qt.io<http://qt.io/>
    > 
    > 
    > 
    > The future is Written with Qt
    >

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to