Jump to content

Telemetry Use: Difference between revisions

From KDE Community Wiki
Argonel (talk | contribs)
m comply with mediawiki style requirements, H1 is for page title only
Apol (talk | contribs)
No edit summary
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Note that all telemetry is '''opt-in'''.
== Plasma ==
== Plasma ==
# '''Application version''': to know if our users are up to date
# '''Application version''': to know if our users are up to date
# '''Compiler information''': to know if issues in non-mainstream compilers are relevant
# '''Compiler information''': to know if issues in non-mainstream compilers are relevant
# '''Platform information''': to know how popular the Wayland session is compared to X11
# '''Platform information''': to know how popular the Wayland session is compared to X11
# '''Qt version''': To how different versions of Qt and Plasma interrelate
# '''Qt version''': to know how different versions of Qt and Plasma interrelate
# '''Usage time''': to find out how many users are using the software heavily vs in passing
# '''Usage time''': to find out how many users are using the software heavily vs in passing
# '''OpenGL version and vendor information''': to learn about our users' hardware; can we trust users to have proper 3D acceleration? Which drivers should be testing? Do people prefer open drivers?
# '''OpenGL version and vendor information''': to learn about our users' hardware; can we trust users to have proper 3D acceleration? Which drivers should be testing? Do people prefer open drivers?
Line 11: Line 13:
# '''Application Source Name (Plasma Discover)''': to find out where users prefer to get their software from
# '''Application Source Name (Plasma Discover)''': to find out where users prefer to get their software from


== Kate (starting with Release 20.04) ==
== Kate (starting with Release 20.04) & KWrite (starting with Release 22.08) ==
 
=== Opt-In Telemetry Information ===
 
# '''Application version''': to know which application versions are still in use
# '''Application version''': to know which application versions are still in use
# '''Qt version''': to know the underlying Qt version (e.g. to see how important workarounds for old issues are)
# '''Qt version''': to know the underlying Qt version (e.g. to see how important workarounds for old issues are)
Line 23: Line 22:


=== Reviews for the introduction/changes of telemetry data submission ===
=== Reviews for the introduction/changes of telemetry data submission ===
* Initial introduction for Kate
: https://invent.kde.org/kde/kate/merge_requests/60


* Initial introduction
* Initial introduction for KWrite
: https://invent.kde.org/kde/kate/merge_requests/60
: https://invent.kde.org/utilities/kate/-/merge_requests/692


== Pim (starting with Release 20.04) ==
== Pim (starting with Release 20.04) ==
=== Opt-In Telemetry Information ===


==== KMail ====
==== KMail ====
Line 51: Line 50:


== Ruqola ==
== Ruqola ==
=== Opt-In Telemetry Information ===
# '''Application version''': to know which application versions are still in use
# '''Application version''': to know which application versions are still in use
# '''Qt version''': to know the underlying Qt version (e.g. to see how important workarounds for old issues are)
# '''Qt version''': to know the underlying Qt version (e.g. to see how important workarounds for old issues are)

Latest revision as of 22:16, 19 May 2024

Note that all telemetry is opt-in.

Plasma

  1. Application version: to know if our users are up to date
  2. Compiler information: to know if issues in non-mainstream compilers are relevant
  3. Platform information: to know how popular the Wayland session is compared to X11
  4. Qt version: to know how different versions of Qt and Plasma interrelate
  5. Usage time: to find out how many users are using the software heavily vs in passing
  6. OpenGL version and vendor information: to learn about our users' hardware; can we trust users to have proper 3D acceleration? Which drivers should be testing? Do people prefer open drivers?
  7. Locale information: To find out if people from different locales are struggling to use Plasma. Are we not getting bug reports because they just don't even consider using it?
  8. Screen parameters: to find out how common multi-screen usage is in Plasma
  9. Panel Count (Plasma Shell): to find out how common it is for people to customize their Panels
  10. Application Source Name (Plasma Discover): to find out where users prefer to get their software from

Kate (starting with Release 20.04) & KWrite (starting with Release 22.08)

  1. Application version: to know which application versions are still in use
  2. Qt version: to know the underlying Qt version (e.g. to see how important workarounds for old issues are)
  3. Platform information: to know the operating system we are running on
  4. Screen parameters: to find out how common multi-screen usage is
  5. Start count: to find out how frequent users use our editor
  6. Usage time: to find out how many users are using the software heavily vs in passing

Reviews for the introduction/changes of telemetry data submission

  • Initial introduction for Kate
https://invent.kde.org/kde/kate/merge_requests/60
  • Initial introduction for KWrite
https://invent.kde.org/utilities/kate/-/merge_requests/692

Pim (starting with Release 20.04)

KMail

  1. Application version: to know which application versions are still in use
  2. Qt version: to know the underlying Qt version (e.g. to see how important workarounds for old issues are)
  3. Platform information: to know the operating system we are running on
  4. Screen parameters: to find out how common multi-screen usage is
  5. Start count: to find out how frequent users use our editor
  6. Usage time: to find out how many users are using the software heavily vs in passing
  7. Locale information: To find out if people uses different locale
  8. Account type information: To find out if people uses different sending account type and receiving account type

Akregator/SieveEditor/Kaddressbook/Korganizer

  1. Application version: to know which application versions are still in use
  2. Qt version: to know the underlying Qt version (e.g. to see how important workarounds for old issues are)
  3. Platform information: to know the operating system we are running on
  4. Screen parameters: to find out how common multi-screen usage is
  5. Start count: to find out how frequent users use our editor
  6. Usage time: to find out how many users are using the software heavily vs in passing
  7. Locale information: To find out if people uses different locale

Ruqola

  1. Application version: to know which application versions are still in use
  2. Qt version: to know the underlying Qt version (e.g. to see how important workarounds for old issues are)
  3. Platform information: to know the operating system we are running on
  4. Screen parameters: to find out how common multi-screen usage is
  5. Start count: to find out how frequent users use our editor
  6. Usage time: to find out how many users are using the software heavily vs in passing
  7. Locale information: To find out if people uses different locale