F40 Change Request: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

[catanzaro (Michael Catanzaro)]

@supakeen

Perhaps this is implicit in the use of eos-* but I seem to be missing a list of what metrics would be collected exactly and what is contained in messages to/from Fedora infrastructure related to these metrics.

I’m not proposing to collect any of these particular metrics just
yet, because a process for Fedora community approval of metrics to be
collected does not yet exist.

Is this change request meant to discuss the general idea and acceptance level of adding opt-out metrics collection in Fedora?

Right. Also, to start discussion of how particular metrics should be approved. I don’t intend to propose collection of any particular metrics until we have some agreement on how exactly metrics should be approved.

Could you please motivate on how metrics collection on which IDE is ran on Fedora systems would help Red Hat achieve making Fedora the premier developer platform for cloud software development?

For example: we’ve been investing in developing tools like GNOME Builder and Toolbx. How much are these tools being used? Do we need to increase or reduce investment in these areas?

Fedora is upstream; collecting these metrics on RHEL systems seems like a saner place to put them if it’s to steer Red Hat prioritizations?

We already have a separate telemetry system for RHEL (Red Hat Insights) that, among other purposes, is used to prioritize RHEL development. But the system I’m proposing here would be for Fedora, not for RHEL. RHEL users are very different from Fedora users, and desktop development should primarily prioritize the needs of Fedora users.