Discussion:
Requesting repos for Connected Creator plugin and telemetry library
(too old to reply)
Tino Pyssysalo
2018-07-16 07:17:19 UTC
Permalink
Hi all,

In March this year, I requested a repo for an open source telemetry plugin for Qt Creator. Now, the plugin has been implemented and I’d like to request two repos:

* A repo for a Connected Creator plugin
* A playground repo for a telemetry library



Description: The Qt Company wants to collect usage data from Qt development tools. For that purpose, we have developed a general-purpose telemetry library and a Qt Creator -specific plugin, using the telemetry library. The reason to collect the data from our users is to learn, how developers use Qt Creator and other tools, how usage patterns change, how quickly new features and versions are started to be used, which tools are mostly used? This information is one data source, helping us to make decisions, how to further develop our products. In the short run, we believe we will get valuable information, how to improve the user experience of our products.



The connected creator plugin implements the frontend for tracking the data from different data sources in Qt Creator. The frontend consists of a simple UI to enable/disable the plugin, to set logs expiration period, and to view the data to be transmitted or previously transmitted data (logs). Currently, the plugin tracks Qt Quick Designer usage only: launch count and usage time. General platform data is collected by the telemetry library. This data currently includes compiler details, locale, OpenGL type and version, Qt version, screen details, Qt Creator version, license type (evaluation, commercial, no license), and unique id (generated with QUuid).



All collected data is anonymous. No personal data such as project names, project locations and paths, IP or MAC addresses, email addresses or Qt Account details are collected.



The data is stored in the backend server, owned by The Qt Company. The backend is complexly separated from the telemetry frontend and the code will be provided in The Qt Company private repo: https://github.com/TheQtCompany/qt-telemetry-backend.



The collected data is cached into a settings file before the transmission. This allows the user to check, what data is going to be transmitted and even disable the plugin before any data is actually transmitted. In addition, data caching allows calculating key values in the frontend instead of sending each user event to the server separately. This reduces the network traffic significantly. By default, the cached data is transmitted to the server once per week. It is possible to log the transmitted data into the files to verify all the data transmitted to the server.



The plugin is planned to be completely opt-in. The online installer will ask the user, if he/she wants to install the plugin. There is no default selection for the installation, but user must explicitly choose either to install or not install the plugin. If the user decides to install the plugin, it can be disabled in Qt Creator settings. The user is able to see the cached data and before the first transmission, the user can disable the plugin, even though it has been installed.



More implementation details can be found in Jira ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250



Existing repos:

Connected Creator plugin: https://github.com/akontsevich/ConnectedCreatorPlugin

Telemetry library: https://github.com/akontsevich/QTelemetry



Responsible: Tino Pyssysalo



Requested repos:

Connected Creator plugin: qt-cresator/plugin-connectedcreator

Telemetry library: playground/telemetry

---
Tino Pyssysalo
Senior Manager
Product Management

The Qt Company
***@qt.io<mailto:***@qt.io>
http://qt.io<http://qt.io/>

The future is Written with Qt
---
Tuukka Turunen
2018-08-30 10:50:45 UTC
Permalink
Hi,

There were no objection to this, request. However, perhaps due to the summertime the repos were not created.

Let’s make those now and move this code under the Qt project.

Yours,

Tuukka

From: Qt-creator <qt-creator-bounces+tuukka.turunen=***@qt-project.org> on behalf of Tino Pyssysalo <***@qt.io>
Date: Monday, 16 July 2018 at 10.17
To: "qt-***@qt-project.org" <qt-***@qt-project.org>
Subject: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library


Hi all,

In March this year, I requested a repo for an open source telemetry plugin for Qt Creator. Now, the plugin has been implemented and I’d like to request two repos:

· A repo for a Connected Creator plugin

· A playground repo for a telemetry library



Description: The Qt Company wants to collect usage data from Qt development tools. For that purpose, we have developed a general-purpose telemetry library and a Qt Creator -specific plugin, using the telemetry library. The reason to collect the data from our users is to learn, how developers use Qt Creator and other tools, how usage patterns change, how quickly new features and versions are started to be used, which tools are mostly used? This information is one data source, helping us to make decisions, how to further develop our products. In the short run, we believe we will get valuable information, how to improve the user experience of our products.



The connected creator plugin implements the frontend for tracking the data from different data sources in Qt Creator. The frontend consists of a simple UI to enable/disable the plugin, to set logs expiration period, and to view the data to be transmitted or previously transmitted data (logs). Currently, the plugin tracks Qt Quick Designer usage only: launch count and usage time. General platform data is collected by the telemetry library. This data currently includes compiler details, locale, OpenGL type and version, Qt version, screen details, Qt Creator version, license type (evaluation, commercial, no license), and unique id (generated with QUuid).



All collected data is anonymous. No personal data such as project names, project locations and paths, IP or MAC addresses, email addresses or Qt Account details are collected.



The data is stored in the backend server, owned by The Qt Company. The backend is complexly separated from the telemetry frontend and the code will be provided in The Qt Company private repo: https://github.com/TheQtCompany/qt-telemetry-backend.



The collected data is cached into a settings file before the transmission. This allows the user to check, what data is going to be transmitted and even disable the plugin before any data is actually transmitted. In addition, data caching allows calculating key values in the frontend instead of sending each user event to the server separately. This reduces the network traffic significantly. By default, the cached data is transmitted to the server once per week. It is possible to log the transmitted data into the files to verify all the data transmitted to the server.



The plugin is planned to be completely opt-in. The online installer will ask the user, if he/she wants to install the plugin. There is no default selection for the installation, but user must explicitly choose either to install or not install the plugin. If the user decides to install the plugin, it can be disabled in Qt Creator settings. The user is able to see the cached data and before the first transmission, the user can disable the plugin, even though it has been installed.



More implementation details can be found in Jira ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250



Existing repos:

Connected Creator plugin: https://github.com/akontsevich/ConnectedCreatorPlugin

Telemetry library: https://github.com/akontsevich/QTelemetry



Responsible: Tino Pyssysalo



Requested repos:

Connected Creator plugin: qt-cresator/plugin-connectedcreator

Telemetry library: playground/telemetry

---
Tino Pyssysalo
Senior Manager
Product Management

The Qt Company
***@qt.io<mailto:***@qt.io>
http://qt.io<http://qt.io/>

The future is Written with Qt
---
Lars Knoll
2018-08-30 10:55:17 UTC
Permalink
Agreed. Frederik, could you help with creating the required repos?

Thanks,
Lars

On 30 Aug 2018, at 12:50, Tuukka Turunen <***@qt.io<mailto:***@qt.io>> wrote:

Hi,

There were no objection to this, request. However, perhaps due to the summertime the repos were not created.

Let’s make those now and move this code under the Qt project.

Yours,

Tuukka

From: Qt-creator <qt-creator-bounces+tuukka.turunen=***@qt-project.org<mailto:qt-creator-bounces+tuukka.turunen=***@qt-project.org>> on behalf of Tino Pyssysalo <***@qt.io<mailto:***@qt.io>>
Date: Monday, 16 July 2018 at 10.17
To: "qt-***@qt-project.org<mailto:qt-***@qt-project.org>" <qt-***@qt-project.org<mailto:qt-***@qt-project.org>>
Subject: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library


Hi all,

In March this year, I requested a repo for an open source telemetry plugin for Qt Creator. Now, the plugin has been implemented and I’d like to request two repos:

• A repo for a Connected Creator plugin

• A playground repo for a telemetry library



Description: The Qt Company wants to collect usage data from Qt development tools. For that purpose, we have developed a general-purpose telemetry library and a Qt Creator -specific plugin, using the telemetry library. The reason to collect the data from our users is to learn, how developers use Qt Creator and other tools, how usage patterns change, how quickly new features and versions are started to be used, which tools are mostly used? This information is one data source, helping us to make decisions, how to further develop our products. In the short run, we believe we will get valuable information, how to improve the user experience of our products.



The connected creator plugin implements the frontend for tracking the data from different data sources in Qt Creator. The frontend consists of a simple UI to enable/disable the plugin, to set logs expiration period, and to view the data to be transmitted or previously transmitted data (logs). Currently, the plugin tracks Qt Quick Designer usage only: launch count and usage time. General platform data is collected by the telemetry library. This data currently includes compiler details, locale, OpenGL type and version, Qt version, screen details, Qt Creator version, license type (evaluation, commercial, no license), and unique id (generated with QUuid).



All collected data is anonymous. No personal data such as project names, project locations and paths, IP or MAC addresses, email addresses or Qt Account details are collected.



The data is stored in the backend server, owned by The Qt Company. The backend is complexly separated from the telemetry frontend and the code will be provided in The Qt Company private repo: https://github.com/TheQtCompany/qt-telemetry-backend.



The collected data is cached into a settings file before the transmission. This allows the user to check, what data is going to be transmitted and even disable the plugin before any data is actually transmitted. In addition, data caching allows calculating key values in the frontend instead of sending each user event to the server separately. This reduces the network traffic significantly. By default, the cached data is transmitted to the server once per week. It is possible to log the transmitted data into the files to verify all the data transmitted to the server.



The plugin is planned to be completely opt-in. The online installer will ask the user, if he/she wants to install the plugin. There is no default selection for the installation, but user must explicitly choose either to install or not install the plugin. If the user decides to install the plugin, it can be disabled in Qt Creator settings. The user is able to see the cached data and before the first transmission, the user can disable the plugin, even though it has been installed.



More implementation details can be found in Jira ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250



Existing repos:

Connected Creator plugin: https://github.com/akontsevich/ConnectedCreatorPlugin

Telemetry library: https://github.com/akontsevich/QTelemetry



Responsible: Tino Pyssysalo



Requested repos:

Connected Creator plugin: qt-cresator/plugin-connectedcreator

Telemetry library: playground/telemetry


---
Tino Pyssysalo
Senior Manager
Product Management

The Qt Company
***@qt.io<mailto:***@qt.io>
http://qt.io<http://qt.io/>

The future is Written with Qt
---
Frederik Gladhorn
2018-08-30 15:20:36 UTC
Permalink
Post by Lars Knoll
Agreed. Frederik, could you help with creating the required repos?
I can create the repos. How do you imagine importing the existing code,
assuming that's the idea?
Should this be a clone of the existing stuff or fresh repos where we start
with a review of the existing code bases?
Post by Lars Knoll
Connected Creator plugin: qt-cresator/plugin-connectedcreator
I'd suggest: qt-creator/plugin-telemetry
Post by Lars Knoll
Telemetry library: playground/telemetry
If this is supposed to become an official Qt library at some point, it should
probably be something like qttelemetry, but starting in playground would means
it needs moving and renaming eventually in any case. The closer we can get to
the final location, the better.

Cheers,
Frederik
Post by Lars Knoll
Thanks,
Lars
Hi,
There were no objection to this, request. However, perhaps due to the
summertime the repos were not created.
Let’s make those now and move this code under the Qt project.
Yours,
Tuukka
at 10.17
Subject: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library
Hi all,
In March this year, I requested a repo for an open source telemetry plugin
for Qt Creator. Now, the plugin has been implemented and I’d like to
request two repos: · A repo for a Connected Creator plugin
· A playground repo for a telemetry library
Description: The Qt Company wants to collect usage data from Qt development
tools. For that purpose, we have developed a general-purpose telemetry
library and a Qt Creator -specific plugin, using the telemetry library. The
reason to collect the data from our users is to learn, how developers use
Qt Creator and other tools, how usage patterns change, how quickly new
features and versions are started to be used, which tools are mostly used?
This information is one data source, helping us to make decisions, how to
further develop our products. In the short run, we believe we will get
valuable information, how to improve the user experience of our products.
The connected creator plugin implements the frontend for tracking the data
from different data sources in Qt Creator. The frontend consists of a
simple UI to enable/disable the plugin, to set logs expiration period, and
to view the data to be transmitted or previously transmitted data (logs).
Currently, the plugin tracks Qt Quick Designer usage only: launch count and
usage time. General platform data is collected by the telemetry library.
This data currently includes compiler details, locale, OpenGL type and
version, Qt version, screen details, Qt Creator version, license type
(evaluation, commercial, no license), and unique id (generated with QUuid).
All collected data is anonymous. No personal data such as project names,
project locations and paths, IP or MAC addresses, email addresses or Qt
Account details are collected.
The data is stored in the backend server, owned by The Qt Company. The
backend is complexly separated from the telemetry frontend and the code
will be provided in The Qt Company
private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
The collected data is cached into a settings file before the transmission.
This allows the user to check, what data is going to be transmitted and
even disable the plugin before any data is actually transmitted. In
addition, data caching allows calculating key values in the frontend
instead of sending each user event to the server separately. This reduces
the network traffic significantly. By default, the cached data is
transmitted to the server once per week. It is possible to log the
transmitted data into the files to verify all the data transmitted to the
server.
The plugin is planned to be completely opt-in. The online installer will ask
the user, if he/she wants to install the plugin. There is no default
selection for the installation, but user must explicitly choose either to
install or not install the plugin. If the user decides to install the
plugin, it can be disabled in Qt Creator settings. The user is able to see
the cached data and before the first transmission, the user can disable the
plugin, even though it has been installed.
More implementation details can be found in Jira
ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
Connected Creator
plugin: https://github.com/akontsevich/ConnectedCreatorPlugin Telemetry
library: https://github.com/akontsevich/QTelemetry
Responsible: Tino Pyssysalo
Connected Creator plugin: qt-cresator/plugin-connectedcreator
Telemetry library: playground/telemetry
---
Tino Pyssysalo
Senior Manager
Product Management
The Qt Company
http://qt.io
The future is Written with Qt
---
Aleksey Kontsevich
2018-08-30 15:39:06 UTC
Permalink
_______________________________________________
Qt-creator mailing list
Qt-***@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
Eike Ziller
2018-08-31 11:29:26 UTC
Permalink
Post by Tuukka Turunen
Hi,
There were no objection to this, request. However, perhaps due to the summertime the repos were not created.
Note that this obviously wasn’t posted on the qt-development mailing list, but on the qt-creator mailing list.
Post by Tuukka Turunen
Let’s make those now and move this code under the Qt project.
Yours,
Tuukka
Date: Monday, 16 July 2018 at 10.17
Subject: [Qt-creator] Requesting repos for Connected Creator plugin and telemetry library
Hi all,
· A repo for a Connected Creator plugin
· A playground repo for a telemetry library
Description: The Qt Company wants to collect usage data from Qt development tools. For that purpose, we have developed a general-purpose telemetry library and a Qt Creator -specific plugin, using the telemetry library. The reason to collect the data from our users is to learn, how developers use Qt Creator and other tools, how usage patterns change, how quickly new features and versions are started to be used, which tools are mostly used? This information is one data source, helping us to make decisions, how to further develop our products. In the short run, we believe we will get valuable information, how to improve the user experience of our products.
The connected creator plugin implements the frontend for tracking the data from different data sources in Qt Creator. The frontend consists of a simple UI to enable/disable the plugin, to set logs expiration period, and to view the data to be transmitted or previously transmitted data (logs). Currently, the plugin tracks Qt Quick Designer usage only: launch count and usage time. General platform data is collected by the telemetry library. This data currently includes compiler details, locale, OpenGL type and version, Qt version, screen details, Qt Creator version, license type (evaluation, commercial, no license), and unique id (generated with QUuid).
All collected data is anonymous. No personal data such as project names, project locations and paths, IP or MAC addresses, email addresses or Qt Account details are collected.
The data is stored in the backend server, owned by The Qt Company. The backend is complexly separated from the telemetry frontend and the code will be provided in The Qt Company private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
The collected data is cached into a settings file before the transmission. This allows the user to check, what data is going to be transmitted and even disable the plugin before any data is actually transmitted. In addition, data caching allows calculating key values in the frontend instead of sending each user event to the server separately. This reduces the network traffic significantly. By default, the cached data is transmitted to the server once per week. It is possible to log the transmitted data into the files to verify all the data transmitted to the server.
The plugin is planned to be completely opt-in. The online installer will ask the user, if he/she wants to install the plugin. There is no default selection for the installation, but user must explicitly choose either to install or not install the plugin. If the user decides to install the plugin, it can be disabled in Qt Creator settings. The user is able to see the cached data and before the first transmission, the user can disable the plugin, even though it has been installed.
More implementation details can be found in Jira ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
Connected Creator plugin: https://github.com/akontsevich/ConnectedCreatorPlugin
Telemetry library: https://github.com/akontsevich/QTelemetry
Responsible: Tino Pyssysalo
Connected Creator plugin: qt-cresator/plugin-connectedcreator
Telemetry library: playground/telemetry
---
Tino Pyssysalo
Senior Manager
Product Management
The Qt Company
http://qt.io
The future is Written with Qt
---
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
--
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
***@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
Aleksey Kontsevich
2018-08-30 15:40:14 UTC
Permalink
You need 2 repos - clones of following:
https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
https://github.com/akontsevich/QTelemetry - the library - QTelemetry name

-- 
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
Post by Frederik Gladhorn
 Agreed. Frederik, could you help with creating the required repos?
I can create the repos. How do you imagine importing the existing code,
assuming that's the idea?
Should this be a clone of the existing stuff or fresh repos where we start
with a review of the existing code bases?
 Connected Creator plugin: qt-cresator/plugin-connectedcreator
I'd suggest: qt-creator/plugin-telemetry
 Telemetry library: playground/telemetry
If this is supposed to become an official Qt library at some point, it should
probably be something like qttelemetry, but starting in playground would means
it needs moving and renaming eventually in any case. The closer we can get to
the final location, the better.
Cheers,
Frederik
 Thanks,
 Lars
 Hi,
 There were no objection to this, request. However, perhaps due to the
 summertime the repos were not created.
 Let’s make those now and move this code under the Qt project.
 Yours,
                 Tuukka
 at 10.17
 Subject: [Qt-creator] Requesting repos for Connected Creator plugin and
 telemetry library
 Hi all,
 In March this year, I requested a repo for an open source telemetry plugin
 for Qt Creator. Now, the plugin has been implemented and I’d like to
 request two repos: · A repo for a Connected Creator plugin
 · A playground repo for a telemetry library
 Description: The Qt Company wants to collect usage data from Qt development
 tools. For that purpose, we have developed a general-purpose telemetry
 library and a Qt Creator -specific plugin, using the telemetry library. The
 reason to collect the data from our users is to learn, how developers use
 Qt Creator and other tools, how usage patterns change, how quickly new
 features and versions are started to be used, which tools are mostly used?
 This information is one data source, helping us to make decisions, how to
 further develop our products. In the short run, we believe we will get
 valuable information, how to improve the user experience of our products.
 The connected creator plugin implements the frontend for tracking the data
 from different data sources in Qt Creator. The frontend consists of a
 simple UI to enable/disable the plugin, to set logs expiration period, and
 to view the data to be transmitted or previously transmitted data (logs).
 Currently, the plugin tracks Qt Quick Designer usage only: launch count and
 usage time. General platform data is collected by the telemetry library.
 This data currently includes compiler details, locale, OpenGL type and
 version, Qt version, screen details, Qt Creator version, license type
 (evaluation, commercial, no license), and unique id (generated with QUuid).
 All collected data is anonymous. No personal data such as project names,
 project locations and paths, IP or MAC addresses, email addresses or Qt
 Account details are collected.
 The data is stored in the backend server, owned by The Qt Company. The
 backend is complexly separated from the telemetry frontend and the code
 will be provided in The Qt Company
 private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
 The collected data is cached into a settings file before the transmission.
 This allows the user to check, what data is going to be transmitted and
 even disable the plugin before any data is actually transmitted. In
 addition, data caching allows calculating key values in the frontend
 instead of sending each user event to the server separately. This reduces
 the network traffic significantly. By default, the cached data is
 transmitted to the server once per week. It is possible to log the
 transmitted data into the files to verify all the data transmitted to the
 server.
 The plugin is planned to be completely opt-in. The online installer will ask
 the user, if he/she wants to install the plugin. There is no default
 selection for the installation, but user must explicitly choose either to
 install or not install the plugin. If the user decides to install the
 plugin, it can be disabled in Qt Creator settings. The user is able to see
 the cached data and before the first transmission, the user can disable the
 plugin, even though it has been installed.
 More implementation details can be found in Jira
 ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
 Connected Creator
 plugin: https://github.com/akontsevich/ConnectedCreatorPlugin Telemetry
 library: https://github.com/akontsevich/QTelemetry
 Responsible: Tino Pyssysalo
 Connected Creator plugin: qt-cresator/plugin-connectedcreator
 Telemetry library: playground/telemetry
 ---
 Tino Pyssysalo
 Senior Manager
 Product Management
 The Qt Company
 http://qt.io
 The future is Written with Qt
 ---
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
,

_______________________________________________
Qt-creator mailing list
Qt-***@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

-------- Конец пересылаемого сообщения --------


-- 
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
Frederik Gladhorn
2018-08-31 11:02:46 UTC
Permalink
Post by Aleksey Kontsevich
https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
I'm not sure I want to clone the repos directly, how will reviews happen?
Should there be a merge request? Is anyone interested in reviewing the whole
stuff and how?

Then most files I peaked into were lacking the license header and in the root
directory I only found a LGPL license (I may be wrong, I didn't spend very
long looking), so that's also not compatible with Qt license policy.

So the question stands, how should the import/review happen?

Cheers,
Frederik
Post by Aleksey Kontsevich
--
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
Post by Frederik Gladhorn
Post by Lars Knoll
Agreed. Frederik, could you help with creating the required repos?
I can create the repos. How do you imagine importing the existing code,
assuming that's the idea?
Should this be a clone of the existing stuff or fresh repos where we start
with a review of the existing code bases?
Post by Lars Knoll
Connected Creator plugin: qt-cresator/plugin-connectedcreator
I'd suggest: qt-creator/plugin-telemetry
Post by Lars Knoll
Telemetry library: playground/telemetry
If this is supposed to become an official Qt library at some point, it
should probably be something like qttelemetry, but starting in playground
would means it needs moving and renaming eventually in any case. The
closer we can get to the final location, the better.
Cheers,
Frederik
Post by Lars Knoll
Thanks,
Lars
Hi,
There were no objection to this, request. However, perhaps due to the
summertime the repos were not created.
Let’s make those now and move this code under the Qt project.
Yours,
Tuukka
From: Qt-creator
10.17
Subject: [Qt-creator] Requesting repos for Connected Creator plugin and
telemetry library
Hi all,
In March this year, I requested a repo for an open source telemetry
plugin
for Qt Creator. Now, the plugin has been implemented and I’d like to
request two repos: · A repo for a Connected Creator plugin
· A playground repo for a telemetry library
Description: The Qt Company wants to collect usage data from Qt
development tools. For that purpose, we have developed a general-purpose
telemetry library and a Qt Creator -specific plugin, using the telemetry
library. The reason to collect the data from our users is to learn, how
developers use Qt Creator and other tools, how usage patterns change,
how quickly new features and versions are started to be used, which
tools are mostly used? This information is one data source, helping us
to make decisions, how to further develop our products. In the short
run, we believe we will get valuable information, how to improve the
user experience of our products. The connected creator plugin implements
the frontend for tracking the data from different data sources in Qt
Creator. The frontend consists of a simple UI to enable/disable the
plugin, to set logs expiration period, and to view the data to be
transmitted or previously transmitted data (logs). Currently, the plugin
tracks Qt Quick Designer usage only: launch count and usage time.
General platform data is collected by the telemetry library. This data
currently includes compiler details, locale, OpenGL type and version, Qt
version, screen details, Qt Creator version, license type (evaluation,
commercial, no license), and unique id (generated with QUuid).
All collected data is anonymous. No personal data such as project names,
project locations and paths, IP or MAC addresses, email addresses or Qt
Account details are collected.
The data is stored in the backend server, owned by The Qt Company. The
backend is complexly separated from the telemetry frontend and the code
will be provided in The Qt Company
private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
The collected data is cached into a settings file before the
transmission.
This allows the user to check, what data is going to be transmitted and
even disable the plugin before any data is actually transmitted. In
addition, data caching allows calculating key values in the frontend
instead of sending each user event to the server separately. This
reduces
the network traffic significantly. By default, the cached data is
transmitted to the server once per week. It is possible to log the
transmitted data into the files to verify all the data transmitted to
the
server.
The plugin is planned to be completely opt-in. The online installer will
ask the user, if he/she wants to install the plugin. There is no default
selection for the installation, but user must explicitly choose either
to install or not install the plugin. If the user decides to install the
plugin, it can be disabled in Qt Creator settings. The user is able to
see the cached data and before the first transmission, the user can
disable the plugin, even though it has been installed.
More implementation details can be found in Jira
ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
Connected Creator
plugin: https://github.com/akontsevich/ConnectedCreatorPlugin Telemetry
library: https://github.com/akontsevich/QTelemetry
Responsible: Tino Pyssysalo
Connected Creator plugin: qt-cresator/plugin-connectedcreator
Telemetry library: playground/telemetry
---
Tino Pyssysalo
Senior Manager
Product Management
The Qt Company
http://qt.io
The future is Written with Qt
---
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
,
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
-------- Конец пересылаемого сообщения --------
--
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
Aleksey Kontsevich
2018-08-31 11:55:16 UTC
Permalink
License header could be easily added and license is LGPL-3.0 which should not be a problem.

-- 
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
Post by Frederik Gladhorn
 https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
 https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
I'm not sure I want to clone the repos directly, how will reviews happen?
Should there be a merge request? Is anyone interested in reviewing the whole
stuff and how?
Then most files I peaked into were lacking the license header and in the root
directory I only found a LGPL license (I may be wrong, I didn't spend very
long looking), so that's also not compatible with Qt license policy.
So the question stands, how should the import/review happen?
Cheers,
Frederik
 --
 Best regards,
 Aleksey
 Linked in https://www.linkedin.com/in/alekseykontsevich
 >> Agreed. Frederik, could you help with creating the required repos?
 >
 > I can create the repos. How do you imagine importing the existing code,
 > assuming that's the idea?
 > Should this be a clone of the existing stuff or fresh repos where we start
 > with a review of the existing code bases?
 >
 >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
 >
 > I'd suggest: qt-creator/plugin-telemetry
 >
 >> Telemetry library: playground/telemetry
 >
 > If this is supposed to become an official Qt library at some point, it
 > should probably be something like qttelemetry, but starting in playground
 > would means it needs moving and renaming eventually in any case. The
 > closer we can get to the final location, the better.
 >
 > Cheers,
 > Frederik
 >
 >> Thanks,
 >> Lars
 >>
 >>
 >> Hi,
 >>
 >> There were no objection to this, request. However, perhaps due to the
 >> summertime the repos were not created.
 >> Let’s make those now and move this code under the Qt project.
 >>
 >> Yours,
 >>
 >> Tuukka
 >>
 >> From: Qt-creator
 >> 10.17
 >> Subject: [Qt-creator] Requesting repos for Connected Creator plugin and
 >> telemetry library
 >> Hi all,
 >>
 >> In March this year, I requested a repo for an open source telemetry
 >> plugin
 >> for Qt Creator. Now, the plugin has been implemented and I’d like to
 >> request two repos: · A repo for a Connected Creator plugin
 >> · A playground repo for a telemetry library
 >>
 >> Description: The Qt Company wants to collect usage data from Qt
 >> development tools. For that purpose, we have developed a general-purpose
 >> telemetry library and a Qt Creator -specific plugin, using the telemetry
 >> library. The reason to collect the data from our users is to learn, how
 >> developers use Qt Creator and other tools, how usage patterns change,
 >> how quickly new features and versions are started to be used, which
 >> tools are mostly used? This information is one data source, helping us
 >> to make decisions, how to further develop our products. In the short
 >> run, we believe we will get valuable information, how to improve the
 >> user experience of our products. The connected creator plugin implements
 >> the frontend for tracking the data from different data sources in Qt
 >> Creator. The frontend consists of a simple UI to enable/disable the
 >> plugin, to set logs expiration period, and to view the data to be
 >> transmitted or previously transmitted data (logs). Currently, the plugin
 >> tracks Qt Quick Designer usage only: launch count and usage time.
 >> General platform data is collected by the telemetry library. This data
 >> currently includes compiler details, locale, OpenGL type and version, Qt
 >> version, screen details, Qt Creator version, license type (evaluation,
 >> commercial, no license), and unique id (generated with QUuid).
 >>
 >> All collected data is anonymous. No personal data such as project names,
 >> project locations and paths, IP or MAC addresses, email addresses or Qt
 >> Account details are collected.
 >> The data is stored in the backend server, owned by The Qt Company. The
 >> backend is complexly separated from the telemetry frontend and the code
 >> will be provided in The Qt Company
 >> private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
 >> The collected data is cached into a settings file before the
 >> transmission.
 >> This allows the user to check, what data is going to be transmitted and
 >> even disable the plugin before any data is actually transmitted. In
 >> addition, data caching allows calculating key values in the frontend
 >> instead of sending each user event to the server separately. This
 >> reduces
 >> the network traffic significantly. By default, the cached data is
 >> transmitted to the server once per week. It is possible to log the
 >> transmitted data into the files to verify all the data transmitted to
 >> the
 >> server.
 >> The plugin is planned to be completely opt-in. The online installer will
 >> ask the user, if he/she wants to install the plugin. There is no default
 >> selection for the installation, but user must explicitly choose either
 >> to install or not install the plugin. If the user decides to install the
 >> plugin, it can be disabled in Qt Creator settings. The user is able to
 >> see the cached data and before the first transmission, the user can
 >> disable the plugin, even though it has been installed.
 >> More implementation details can be found in Jira
 >> ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
 >> Connected Creator
 >> plugin: https://github.com/akontsevich/ConnectedCreatorPlugin Telemetry
 >> library: https://github.com/akontsevich/QTelemetry
 >>
 >> Responsible: Tino Pyssysalo
 >>
 >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
 >> Telemetry library: playground/telemetry
 >>
 >> ---
 >> Tino Pyssysalo
 >> Senior Manager
 >> Product Management
 >>
 >> The Qt Company
 >> http://qt.io
 >>
 >> The future is Written with Qt
 >> ---
 >
 > _______________________________________________
 > Qt-creator mailing list
 > http://lists.qt-project.org/mailman/listinfo/qt-creator
 ,
 _______________________________________________
 Qt-creator mailing list
 http://lists.qt-project.org/mailman/listinfo/qt-creator
 -------- Конец пересылаемого сообщения --------
 --
 Best regards,
 Aleksey
 Linked in https://www.linkedin.com/in/alekseykontsevich
 _______________________________________________
 Qt-creator mailing list
 http://lists.qt-project.org/mailman/listinfo/qt-creator
Frederik Gladhorn
2018-09-04 09:24:30 UTC
Permalink
With much joy I created two repositories.

qt-creator/plugin-telemetry
playground/telemetry

They still need concise descriptions as the other repos have, please send them
to me.

Cheers,
Frederik
Post by Frederik Gladhorn
Post by Aleksey Kontsevich
https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
I'm not sure I want to clone the repos directly, how will reviews happen?
Should there be a merge request? Is anyone interested in reviewing the whole
stuff and how?
Then most files I peaked into were lacking the license header and in the
root directory I only found a LGPL license (I may be wrong, I didn't spend
very long looking), so that's also not compatible with Qt license policy.
So the question stands, how should the import/review happen?
Cheers,
Frederik
Post by Aleksey Kontsevich
Post by Frederik Gladhorn
Post by Lars Knoll
Agreed. Frederik, could you help with creating the required repos?
I can create the repos. How do you imagine importing the existing code,
assuming that's the idea?
Should this be a clone of the existing stuff or fresh repos where we start
with a review of the existing code bases?
Post by Lars Knoll
Connected Creator plugin: qt-cresator/plugin-connectedcreator
I'd suggest: qt-creator/plugin-telemetry
Post by Lars Knoll
Telemetry library: playground/telemetry
If this is supposed to become an official Qt library at some point, it
should probably be something like qttelemetry, but starting in playground
would means it needs moving and renaming eventually in any case. The
closer we can get to the final location, the better.
Cheers,
Frederik
Post by Lars Knoll
Thanks,
Lars
Hi,
There were no objection to this, request. However, perhaps due to the
summertime the repos were not created.
Let’s make those now and move this code under the Qt project.
Yours,
Tuukka
From: Qt-creator
10.17
Subject: [Qt-creator] Requesting repos for Connected Creator plugin and
telemetry library
Hi all,
In March this year, I requested a repo for an open source telemetry
plugin
for Qt Creator. Now, the plugin has been implemented and I’d like to
request two repos: · A repo for a Connected Creator plugin
· A playground repo for a telemetry library
Description: The Qt Company wants to collect usage data from Qt
development tools. For that purpose, we have developed a
general-purpose
telemetry library and a Qt Creator -specific plugin, using the telemetry
library. The reason to collect the data from our users is to learn, how
developers use Qt Creator and other tools, how usage patterns change,
how quickly new features and versions are started to be used, which
tools are mostly used? This information is one data source, helping us
to make decisions, how to further develop our products. In the short
run, we believe we will get valuable information, how to improve the
user experience of our products. The connected creator plugin implements
the frontend for tracking the data from different data sources in Qt
Creator. The frontend consists of a simple UI to enable/disable the
plugin, to set logs expiration period, and to view the data to be
transmitted or previously transmitted data (logs). Currently, the plugin
tracks Qt Quick Designer usage only: launch count and usage time.
General platform data is collected by the telemetry library. This data
currently includes compiler details, locale, OpenGL type and version, Qt
version, screen details, Qt Creator version, license type (evaluation,
commercial, no license), and unique id (generated with QUuid).
All collected data is anonymous. No personal data such as project names,
project locations and paths, IP or MAC addresses, email addresses or Qt
Account details are collected.
The data is stored in the backend server, owned by The Qt Company. The
backend is complexly separated from the telemetry frontend and the code
will be provided in The Qt Company
private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
The collected data is cached into a settings file before the
transmission.
This allows the user to check, what data is going to be transmitted and
even disable the plugin before any data is actually transmitted. In
addition, data caching allows calculating key values in the frontend
instead of sending each user event to the server separately. This
reduces
the network traffic significantly. By default, the cached data is
transmitted to the server once per week. It is possible to log the
transmitted data into the files to verify all the data transmitted to
the
server.
The plugin is planned to be completely opt-in. The online installer will
ask the user, if he/she wants to install the plugin. There is no default
selection for the installation, but user must explicitly choose either
to install or not install the plugin. If the user decides to install the
plugin, it can be disabled in Qt Creator settings. The user is able to
see the cached data and before the first transmission, the user can
disable the plugin, even though it has been installed.
More implementation details can be found in Jira
ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
Connected Creator
plugin: https://github.com/akontsevich/ConnectedCreatorPlugin Telemetry
library: https://github.com/akontsevich/QTelemetry
Responsible: Tino Pyssysalo
Connected Creator plugin: qt-cresator/plugin-connectedcreator
Telemetry library: playground/telemetry
---
Tino Pyssysalo
Senior Manager
Product Management
The Qt Company
http://qt.io
The future is Written with Qt
---
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
,
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
-------- Конец пересылаемого сообщения --------
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
Aleksey Kontsevich
2018-09-04 10:20:27 UTC
Permalink
Description for the plugin:
Connected creator plugin collects usage data from Qt Creator users. This data is used to improve Qt user experience and as one information source to make product decisions.

For the library:
Qt library for collecting usage statistics from users for Qt applications via telemetry and submitting the data to REST API server backend

-- 
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
Post by Frederik Gladhorn
With much joy I created two repositories.
qt-creator/plugin-telemetry
playground/telemetry
They still need concise descriptions as the other repos have, please send them
to me.
Cheers,
Frederik
 > https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
 > https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
 I'm not sure I want to clone the repos directly, how will reviews happen?
 Should there be a merge request? Is anyone interested in reviewing the whole
 stuff and how?
 Then most files I peaked into were lacking the license header and in the
 root directory I only found a LGPL license (I may be wrong, I didn't spend
 very long looking), so that's also not compatible with Qt license policy.
 So the question stands, how should the import/review happen?
 Cheers,
 Frederik
 > >> Agreed. Frederik, could you help with creating the required repos?
 > >
 > > I can create the repos. How do you imagine importing the existing code,
 > > assuming that's the idea?
 > > Should this be a clone of the existing stuff or fresh repos where we
 > > start
 > > with a review of the existing code bases?
 > >
 > >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
 > >
 > > I'd suggest: qt-creator/plugin-telemetry
 > >
 > >> Telemetry library: playground/telemetry
 > >
 > > If this is supposed to become an official Qt library at some point, it
 > > should probably be something like qttelemetry, but starting in
 > > playground
 > > would means it needs moving and renaming eventually in any case. The
 > > closer we can get to the final location, the better.
 > >
 > > Cheers,
 > > Frederik
 > >
 > >> Thanks,
 > >> Lars
 > >>
 > >>
 > >> Hi,
 > >>
 > >> There were no objection to this, request. However, perhaps due to the
 > >> summertime the repos were not created.
 > >> Let’s make those now and move this code under the Qt project.
 > >>
 > >> Yours,
 > >>
 > >> Tuukka
 > >>
 > >> From: Qt-creator
 > >>
 > >> 10.17
 > >>
 > >> Subject: [Qt-creator] Requesting repos for Connected Creator plugin
 > >> and
 > >> telemetry library
 > >> Hi all,
 > >>
 > >> In March this year, I requested a repo for an open source telemetry
 > >>
 > >> plugin
 > >>
 > >> for Qt Creator. Now, the plugin has been implemented and I’d like to
 > >> request two repos: · A repo for a Connected Creator plugin
 > >> · A playground repo for a telemetry library
 > >>
 > >> Description: The Qt Company wants to collect usage data from Qt
 > >>
 > >> development tools. For that purpose, we have developed a
 > >> general-purpose
 > >> telemetry library and a Qt Creator -specific plugin, using the
 > >> telemetry
 > >> library. The reason to collect the data from our users is to learn, how
 > >> developers use Qt Creator and other tools, how usage patterns change,
 > >> how quickly new features and versions are started to be used, which
 > >> tools are mostly used? This information is one data source, helping us
 > >> to make decisions, how to further develop our products. In the short
 > >> run, we believe we will get valuable information, how to improve the
 > >> user experience of our products. The connected creator plugin
 > >> implements
 > >> the frontend for tracking the data from different data sources in Qt
 > >> Creator. The frontend consists of a simple UI to enable/disable the
 > >> plugin, to set logs expiration period, and to view the data to be
 > >> transmitted or previously transmitted data (logs). Currently, the
 > >> plugin
 > >> tracks Qt Quick Designer usage only: launch count and usage time.
 > >> General platform data is collected by the telemetry library. This data
 > >> currently includes compiler details, locale, OpenGL type and version,
 > >> Qt
 > >> version, screen details, Qt Creator version, license type (evaluation,
 > >> commercial, no license), and unique id (generated with QUuid).
 > >>
 > >> All collected data is anonymous. No personal data such as project
 > >> names,
 > >> project locations and paths, IP or MAC addresses, email addresses or
 > >> Qt
 > >> Account details are collected.
 > >> The data is stored in the backend server, owned by The Qt Company. The
 > >> backend is complexly separated from the telemetry frontend and the
 > >> code
 > >> will be provided in The Qt Company
 > >> private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
 > >> The collected data is cached into a settings file before the
 > >>
 > >> transmission.
 > >>
 > >> This allows the user to check, what data is going to be transmitted
 > >> and
 > >> even disable the plugin before any data is actually transmitted. In
 > >> addition, data caching allows calculating key values in the frontend
 > >> instead of sending each user event to the server separately. This
 > >>
 > >> reduces
 > >>
 > >> the network traffic significantly. By default, the cached data is
 > >> transmitted to the server once per week. It is possible to log the
 > >> transmitted data into the files to verify all the data transmitted to
 > >>
 > >> the
 > >>
 > >> server.
 > >> The plugin is planned to be completely opt-in. The online installer
 > >> will
 > >>
 > >> ask the user, if he/she wants to install the plugin. There is no
 > >> default
 > >> selection for the installation, but user must explicitly choose either
 > >> to install or not install the plugin. If the user decides to install
 > >> the
 > >> plugin, it can be disabled in Qt Creator settings. The user is able to
 > >> see the cached data and before the first transmission, the user can
 > >> disable the plugin, even though it has been installed.
 > >>
 > >> More implementation details can be found in Jira
 > >> ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
 > >> Connected Creator
 > >> plugin: https://github.com/akontsevich/ConnectedCreatorPlugin
 > >> Telemetry
 > >> library: https://github.com/akontsevich/QTelemetry
 > >>
 > >> Responsible: Tino Pyssysalo
 > >>
 > >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
 > >> Telemetry library: playground/telemetry
 > >>
 > >> ---
 > >> Tino Pyssysalo
 > >> Senior Manager
 > >> Product Management
 > >>
 > >> The Qt Company
 > >> http://qt.io
 > >>
 > >> The future is Written with Qt
 > >> ---
 > >
 > > _______________________________________________
 > > Qt-creator mailing list
 > > http://lists.qt-project.org/mailman/listinfo/qt-creator
 >
 > ,
 >
 > _______________________________________________
 > Qt-creator mailing list
 > http://lists.qt-project.org/mailman/listinfo/qt-creator
 >
 > -------- Конец пересылаемого сообщения --------
 _______________________________________________
 Qt-creator mailing list
 http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
Aleksey Kontsevich
2018-09-28 14:33:20 UTC
Permalink
Thanks all for the repos. Now initial library and plugin commits are on review for both projects:
- https://codereview.qt-project.org/#/c/240347/
- https://codereview.qt-project.org/#/c/240361/

It is good if someone wants to review and approve those cause we need to move things forward and try to include our project into coming QtC 4.8 release.

Thanks all again for participation!

-- 
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
Post by Frederik Gladhorn
With much joy I created two repositories.
qt-creator/plugin-telemetry
playground/telemetry
They still need concise descriptions as the other repos have, please send them
to me.
Cheers,
Frederik
 > https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
 > https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
 I'm not sure I want to clone the repos directly, how will reviews happen?
 Should there be a merge request? Is anyone interested in reviewing the whole
 stuff and how?
 Then most files I peaked into were lacking the license header and in the
 root directory I only found a LGPL license (I may be wrong, I didn't spend
 very long looking), so that's also not compatible with Qt license policy.
 So the question stands, how should the import/review happen?
 Cheers,
 Frederik
 > >> Agreed. Frederik, could you help with creating the required repos?
 > >
 > > I can create the repos. How do you imagine importing the existing code,
 > > assuming that's the idea?
 > > Should this be a clone of the existing stuff or fresh repos where we
 > > start
 > > with a review of the existing code bases?
 > >
 > >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
 > >
 > > I'd suggest: qt-creator/plugin-telemetry
 > >
 > >> Telemetry library: playground/telemetry
 > >
 > > If this is supposed to become an official Qt library at some point, it
 > > should probably be something like qttelemetry, but starting in
 > > playground
 > > would means it needs moving and renaming eventually in any case. The
 > > closer we can get to the final location, the better.
 > >
 > > Cheers,
 > > Frederik
 > >
 > >> Thanks,
 > >> Lars
 > >>
 > >>
 > >> Hi,
 > >>
 > >> There were no objection to this, request. However, perhaps due to the
 > >> summertime the repos were not created.
 > >> Let’s make those now and move this code under the Qt project.
 > >>
 > >> Yours,
 > >>
 > >> Tuukka
 > >>
 > >> From: Qt-creator
 > >>
 > >> 10.17
 > >>
 > >> Subject: [Qt-creator] Requesting repos for Connected Creator plugin
 > >> and
 > >> telemetry library
 > >> Hi all,
 > >>
 > >> In March this year, I requested a repo for an open source telemetry
 > >>
 > >> plugin
 > >>
 > >> for Qt Creator. Now, the plugin has been implemented and I’d like to
 > >> request two repos: · A repo for a Connected Creator plugin
 > >> · A playground repo for a telemetry library
 > >>
 > >> Description: The Qt Company wants to collect usage data from Qt
 > >>
 > >> development tools. For that purpose, we have developed a
 > >> general-purpose
 > >> telemetry library and a Qt Creator -specific plugin, using the
 > >> telemetry
 > >> library. The reason to collect the data from our users is to learn, how
 > >> developers use Qt Creator and other tools, how usage patterns change,
 > >> how quickly new features and versions are started to be used, which
 > >> tools are mostly used? This information is one data source, helping us
 > >> to make decisions, how to further develop our products. In the short
 > >> run, we believe we will get valuable information, how to improve the
 > >> user experience of our products. The connected creator plugin
 > >> implements
 > >> the frontend for tracking the data from different data sources in Qt
 > >> Creator. The frontend consists of a simple UI to enable/disable the
 > >> plugin, to set logs expiration period, and to view the data to be
 > >> transmitted or previously transmitted data (logs). Currently, the
 > >> plugin
 > >> tracks Qt Quick Designer usage only: launch count and usage time.
 > >> General platform data is collected by the telemetry library. This data
 > >> currently includes compiler details, locale, OpenGL type and version,
 > >> Qt
 > >> version, screen details, Qt Creator version, license type (evaluation,
 > >> commercial, no license), and unique id (generated with QUuid).
 > >>
 > >> All collected data is anonymous. No personal data such as project
 > >> names,
 > >> project locations and paths, IP or MAC addresses, email addresses or
 > >> Qt
 > >> Account details are collected.
 > >> The data is stored in the backend server, owned by The Qt Company. The
 > >> backend is complexly separated from the telemetry frontend and the
 > >> code
 > >> will be provided in The Qt Company
 > >> private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
 > >> The collected data is cached into a settings file before the
 > >>
 > >> transmission.
 > >>
 > >> This allows the user to check, what data is going to be transmitted
 > >> and
 > >> even disable the plugin before any data is actually transmitted. In
 > >> addition, data caching allows calculating key values in the frontend
 > >> instead of sending each user event to the server separately. This
 > >>
 > >> reduces
 > >>
 > >> the network traffic significantly. By default, the cached data is
 > >> transmitted to the server once per week. It is possible to log the
 > >> transmitted data into the files to verify all the data transmitted to
 > >>
 > >> the
 > >>
 > >> server.
 > >> The plugin is planned to be completely opt-in. The online installer
 > >> will
 > >>
 > >> ask the user, if he/she wants to install the plugin. There is no
 > >> default
 > >> selection for the installation, but user must explicitly choose either
 > >> to install or not install the plugin. If the user decides to install
 > >> the
 > >> plugin, it can be disabled in Qt Creator settings. The user is able to
 > >> see the cached data and before the first transmission, the user can
 > >> disable the plugin, even though it has been installed.
 > >>
 > >> More implementation details can be found in Jira
 > >> ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
 > >> Connected Creator
 > >> plugin: https://github.com/akontsevich/ConnectedCreatorPlugin
 > >> Telemetry
 > >> library: https://github.com/akontsevich/QTelemetry
 > >>
 > >> Responsible: Tino Pyssysalo
 > >>
 > >> Connected Creator plugin: qt-cresator/plugin-connectedcreator
 > >> Telemetry library: playground/telemetry
 > >>
 > >> ---
 > >> Tino Pyssysalo
 > >> Senior Manager
 > >> Product Management
 > >>
 > >> The Qt Company
 > >> http://qt.io
 > >>
 > >> The future is Written with Qt
 > >> ---
 > >
 > > _______________________________________________
 > > Qt-creator mailing list
 > > http://lists.qt-project.org/mailman/listinfo/qt-creator
 >
 > ,
 >
 > _______________________________________________
 > Qt-creator mailing list
 > http://lists.qt-project.org/mailman/listinfo/qt-creator
 >
 > -------- Конец пересылаемого сообщения --------
 _______________________________________________
 Qt-creator mailing list
 http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
Tuukka Turunen
2018-10-01 11:33:23 UTC
Permalink
Thanks, Aleksey.

Posting this to development list as well.

Yours,

Tuukka

On 28/09/2018, 16.33, "Qt-creator on behalf of Aleksey Kontsevich" <qt-creator-bounces+tuukka.turunen=***@qt-project.org on behalf of ***@ya.ru> wrote:

Thanks all for the repos. Now initial library and plugin commits are on review for both projects:
- https://codereview.qt-project.org/#/c/240347/
- https://codereview.qt-project.org/#/c/240361/

It is good if someone wants to review and approve those cause we need to move things forward and try to include our project into coming QtC 4.8 release.

Thanks all again for participation!

--
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
Post by Frederik Gladhorn
With much joy I created two repositories.
qt-creator/plugin-telemetry
playground/telemetry
They still need concise descriptions as the other repos have, please send them
to me.
Cheers,
Frederik
Post by Frederik Gladhorn
Post by Aleksey Kontsevich
https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
I'm not sure I want to clone the repos directly, how will reviews happen?
Should there be a merge request? Is anyone interested in reviewing the whole
stuff and how?
Then most files I peaked into were lacking the license header and in the
root directory I only found a LGPL license (I may be wrong, I didn't spend
very long looking), so that's also not compatible with Qt license policy.
So the question stands, how should the import/review happen?
Cheers,
Frederik
Post by Aleksey Kontsevich
Post by Frederik Gladhorn
Post by Lars Knoll
Agreed. Frederik, could you help with creating the required repos?
I can create the repos. How do you imagine importing the existing code,
assuming that's the idea?
Should this be a clone of the existing stuff or fresh repos where we start
with a review of the existing code bases?
Post by Lars Knoll
Connected Creator plugin: qt-cresator/plugin-connectedcreator
I'd suggest: qt-creator/plugin-telemetry
Post by Lars Knoll
Telemetry library: playground/telemetry
If this is supposed to become an official Qt library at some point, it
should probably be something like qttelemetry, but starting in playground
would means it needs moving and renaming eventually in any case. The
closer we can get to the final location, the better.
Cheers,
Frederik
Post by Lars Knoll
Thanks,
Lars
Hi,
There were no objection to this, request. However, perhaps due to the
summertime the repos were not created.
Let’s make those now and move this code under the Qt project.
Yours,
Tuukka
From: Qt-creator
10.17
Subject: [Qt-creator] Requesting repos for Connected Creator plugin and
telemetry library
Hi all,
In March this year, I requested a repo for an open source telemetry
plugin
for Qt Creator. Now, the plugin has been implemented and I’d like to
request two repos: · A repo for a Connected Creator plugin
· A playground repo for a telemetry library
Description: The Qt Company wants to collect usage data from Qt
development tools. For that purpose, we have developed a general-purpose
telemetry library and a Qt Creator -specific plugin, using the telemetry
library. The reason to collect the data from our users is to learn, how
developers use Qt Creator and other tools, how usage patterns change,
how quickly new features and versions are started to be used, which
tools are mostly used? This information is one data source, helping us
to make decisions, how to further develop our products. In the short
run, we believe we will get valuable information, how to improve the
user experience of our products. The connected creator plugin implements
the frontend for tracking the data from different data sources in Qt
Creator. The frontend consists of a simple UI to enable/disable the
plugin, to set logs expiration period, and to view the data to be
transmitted or previously transmitted data (logs). Currently, the plugin
tracks Qt Quick Designer usage only: launch count and usage time.
General platform data is collected by the telemetry library. This data
currently includes compiler details, locale, OpenGL type and version, Qt
version, screen details, Qt Creator version, license type (evaluation,
commercial, no license), and unique id (generated with QUuid).
All collected data is anonymous. No personal data such as project names,
project locations and paths, IP or MAC addresses, email addresses or Qt
Account details are collected.
The data is stored in the backend server, owned by The Qt Company. The
backend is complexly separated from the telemetry frontend and the code
will be provided in The Qt Company
private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
The collected data is cached into a settings file before the
transmission.
This allows the user to check, what data is going to be transmitted and
even disable the plugin before any data is actually transmitted. In
addition, data caching allows calculating key values in the frontend
instead of sending each user event to the server separately. This
reduces
the network traffic significantly. By default, the cached data is
transmitted to the server once per week. It is possible to log the
transmitted data into the files to verify all the data transmitted to
the
server.
The plugin is planned to be completely opt-in. The online installer will
ask the user, if he/she wants to install the plugin. There is no default
selection for the installation, but user must explicitly choose either
to install or not install the plugin. If the user decides to install the
plugin, it can be disabled in Qt Creator settings. The user is able to
see the cached data and before the first transmission, the user can
disable the plugin, even though it has been installed.
More implementation details can be found in Jira
ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
Connected Creator
plugin: https://github.com/akontsevich/ConnectedCreatorPlugin Telemetry
library: https://github.com/akontsevich/QTelemetry
Responsible: Tino Pyssysalo
Connected Creator plugin: qt-cresator/plugin-connectedcreator
Telemetry library: playground/telemetry
---
Tino Pyssysalo
Senior Manager
Product Management
The Qt Company
http://qt.io
The future is Written with Qt
---
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
,
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
-------- Конец пересылаемого сообщения --------
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-***@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
Tuukka Turunen
2018-10-01 13:20:08 UTC
Permalink
Thanks, Aleksey.

Posting this to development mailing list as well.

Yours,

Tuukka

On 28/09/2018, 16.33, "Qt-creator on behalf of Aleksey Kontsevich" <qt-creator-bounces+tuukka.turunen=***@qt-project.org on behalf of ***@ya.ru> wrote:

Thanks all for the repos. Now initial library and plugin commits are on review for both projects:
- https://codereview.qt-project.org/#/c/240347/
- https://codereview.qt-project.org/#/c/240361/

It is good if someone wants to review and approve those cause we need to move things forward and try to include our project into coming QtC 4.8 release.

Thanks all again for participation!

--
Best regards,
Aleksey
Linked in https://www.linkedin.com/in/alekseykontsevich
Post by Frederik Gladhorn
With much joy I created two repositories.
qt-creator/plugin-telemetry
playground/telemetry
They still need concise descriptions as the other repos have, please send them
to me.
Cheers,
Frederik
Post by Frederik Gladhorn
Post by Aleksey Kontsevich
https://github.com/akontsevich/ConnectedCreatorPlugin - the QtC plugin
https://github.com/akontsevich/QTelemetry - the library - QTelemetry name
I'm not sure I want to clone the repos directly, how will reviews happen?
Should there be a merge request? Is anyone interested in reviewing the whole
stuff and how?
Then most files I peaked into were lacking the license header and in the
root directory I only found a LGPL license (I may be wrong, I didn't spend
very long looking), so that's also not compatible with Qt license policy.
So the question stands, how should the import/review happen?
Cheers,
Frederik
Post by Aleksey Kontsevich
Post by Frederik Gladhorn
Post by Lars Knoll
Agreed. Frederik, could you help with creating the required repos?
I can create the repos. How do you imagine importing the existing code,
assuming that's the idea?
Should this be a clone of the existing stuff or fresh repos where we start
with a review of the existing code bases?
Post by Lars Knoll
Connected Creator plugin: qt-cresator/plugin-connectedcreator
I'd suggest: qt-creator/plugin-telemetry
Post by Lars Knoll
Telemetry library: playground/telemetry
If this is supposed to become an official Qt library at some point, it
should probably be something like qttelemetry, but starting in playground
would means it needs moving and renaming eventually in any case. The
closer we can get to the final location, the better.
Cheers,
Frederik
Post by Lars Knoll
Thanks,
Lars
Hi,
There were no objection to this, request. However, perhaps due to the
summertime the repos were not created.
Let’s make those now and move this code under the Qt project.
Yours,
Tuukka
From: Qt-creator
10.17
Subject: [Qt-creator] Requesting repos for Connected Creator plugin and
telemetry library
Hi all,
In March this year, I requested a repo for an open source telemetry
plugin
for Qt Creator. Now, the plugin has been implemented and I’d like to
request two repos: · A repo for a Connected Creator plugin
· A playground repo for a telemetry library
Description: The Qt Company wants to collect usage data from Qt
development tools. For that purpose, we have developed a general-purpose
telemetry library and a Qt Creator -specific plugin, using the telemetry
library. The reason to collect the data from our users is to learn, how
developers use Qt Creator and other tools, how usage patterns change,
how quickly new features and versions are started to be used, which
tools are mostly used? This information is one data source, helping us
to make decisions, how to further develop our products. In the short
run, we believe we will get valuable information, how to improve the
user experience of our products. The connected creator plugin implements
the frontend for tracking the data from different data sources in Qt
Creator. The frontend consists of a simple UI to enable/disable the
plugin, to set logs expiration period, and to view the data to be
transmitted or previously transmitted data (logs). Currently, the plugin
tracks Qt Quick Designer usage only: launch count and usage time.
General platform data is collected by the telemetry library. This data
currently includes compiler details, locale, OpenGL type and version, Qt
version, screen details, Qt Creator version, license type (evaluation,
commercial, no license), and unique id (generated with QUuid).
All collected data is anonymous. No personal data such as project names,
project locations and paths, IP or MAC addresses, email addresses or Qt
Account details are collected.
The data is stored in the backend server, owned by The Qt Company. The
backend is complexly separated from the telemetry frontend and the code
will be provided in The Qt Company
private repo: https://github.com/TheQtCompany/qt-telemetry-backend.
The collected data is cached into a settings file before the
transmission.
This allows the user to check, what data is going to be transmitted and
even disable the plugin before any data is actually transmitted. In
addition, data caching allows calculating key values in the frontend
instead of sending each user event to the server separately. This
reduces
the network traffic significantly. By default, the cached data is
transmitted to the server once per week. It is possible to log the
transmitted data into the files to verify all the data transmitted to
the
server.
The plugin is planned to be completely opt-in. The online installer will
ask the user, if he/she wants to install the plugin. There is no default
selection for the installation, but user must explicitly choose either
to install or not install the plugin. If the user decides to install the
plugin, it can be disabled in Qt Creator settings. The user is able to
see the cached data and before the first transmission, the user can
disable the plugin, even though it has been installed.
More implementation details can be found in Jira
ticket: https://bugreports.qt.io/browse/QTCREATORBUG-20250
Connected Creator
plugin: https://github.com/akontsevich/ConnectedCreatorPlugin Telemetry
library: https://github.com/akontsevich/QTelemetry
Responsible: Tino Pyssysalo
Connected Creator plugin: qt-cresator/plugin-connectedcreator
Telemetry library: playground/telemetry
---
Tino Pyssysalo
Senior Manager
Product Management
The Qt Company
http://qt.io
The future is Written with Qt
---
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
,
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
-------- Конец пересылаемого сообщения --------
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
Qt-***@qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator

Loading...