Bug 115712 (Usage-Metrics) - [META] Usability metrics (usage stats) bugs and enhancements
Summary: [META] Usability metrics (usage stats) bugs and enhancements
Status: NEW
Alias: Usage-Metrics
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on: 95505 96434 96438 96439 96440 140107
Blocks: Privacy
  Show dependency treegraph
Reported: 2018-02-14 10:16 UTC by Yousuf Philips (jay) (retired)
Modified: 2022-11-03 09:00 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2018-02-14 10:16:13 UTC

Comment 1 Yousuf Philips (jay) (retired) 2018-02-14 10:33:17 UTC
There was a tender issued by TDF for usability metrics collection, though it was never worked on from what i know.


Created this google doc with details on what data should be collected for usage metrics.

Comment 2 jan d 2021-02-02 18:54:16 UTC
I like the idea of metrics but we currently don't collect them we probably should remove the code. A relatively easy change might be deleting the checkbox to activate it which declutters the settings UI at least a tiny bit.
Comment 3 Adolfo Jayme Barrientos 2022-09-24 05:51:43 UTC
The usage-data collection code was removed and there are no plans to add privacy-invasive telemetry.
Comment 4 Heiko Tietze 2022-11-02 12:31:11 UTC
Let's reactivate the topic as there is new development at https://design.blog.documentfoundation.org/2022/11/01/community-support-needed-we-want-to-use-our-users-personal-data/
Comment 5 Eyal Rozenberg 2022-11-02 20:51:24 UTC
(In reply to Heiko Tietze from comment #4)

I oppose this re-activation, because:

1. The "new development" is a for-profit organization which has a financial interest in doing processing for money on collected user data; and the blog post was made despite an earlier discussion of the initiative failing to reach agreement on pursuing it.

2. Introduction of user monitoring code back into LO is a significant decision with far-reaching consequences. It may even conflict with an appropriate interpretation of "user-centered", i.e. with a tenet of the development community the TDF is purposed to promote. I thus claim that it requires wide consultation of the members and discussion in the BoG.
Comment 6 Adolfo Jayme Barrientos 2022-11-03 09:00:36 UTC
I must say that the blog post and intent has taken me completely by surprise. I am a TDF trustee, so it’s a little disappointing to be blindsided on this.

It is unclear how and if any TDF personnel will act upon any hypothetical data obtained from telemetry, and what are the benefits — will the TDF fund development on UX improvements? Given its track record, you will excuse me for being skeptical.

I don’t care if the TDF as an organization wants to obtain income from corporate partnerships, but please don’t taint the software.