search

ublue-os / bazzite

Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld.
https://bazzite.gg
Apache License 2.0
3.66k stars 217 forks source link

brew.sh analytics default enabled #1597

Open RheaAyase opened 2 weeks ago

RheaAyase commented 2 weeks ago

Describe the bug

https://docs.brew.sh/Analytics is enabled by default

What did you expect to happen?

As it is customary in Fedora, analytics should be disabled by default. https://docs.brew.sh/Analytics

Output of rpm-ostree status

No response

Hardware

No response

Extra information or context

No response

p5 commented 2 weeks ago

I don't think this will be in scope for UBlue.
Creating a ujust script to disable telemetry, maybe. Default disabling them, I'm not sure.

As long as the collected metrics are anonymous and the data gathered is relevant, we prefer to keep the settings stock and be responsible open-source software (OSS) consumers. Telemetry plays a crucial role in helping projects understand how their software is being used and where they should prioritize their efforts.

Brew is also one of the only ways we can see roughly how many users the UBlue projects have :smile:

RheaAyase commented 2 weeks ago

My opinion, take it or leave it :)

Telemetry plays crucial role to projects if the user actually uses it. Brew comes pre-installed, yet nothing that I can see uses it, it's opaque and if it wasn't for scrolling through dmesg I wouldn't even know that it was there. It is not beneficial to any project trying to understand the user counts, having something preinstalled without the knowledge of the user, essentially merely polluting the metrics. At a glance someone might think "oh look, we have 54k users this month" but in reality it was probably "oh look, 54k people happen to have this on their system, out of which only 12k know about it and actually use it." Now i don't know how they gather metrics, but it does run update on a timer which prints the telemetry warning, so I'd assume that they have even such an inactive pre-installed oblivious user logged as a number in their little spreadsheet. Just like a metric of "this month this many people installed our brew product" probably wasn't exactly accurate either, if it came pre-installed.

(Like I said, if it was up to me, brew.sh would NOT be pre-installed in the first place. It isn't necessary, or even useful for vast majority of Bazzite users. Also my opinion.)

KyleGospo commented 2 weeks ago

The brew maintainers ask that the analytics not be changed downstream, but given we're pre installing it may be worth looping them into this conversation to see what they recommend.

We install brew because it solves for the CLI what flatpak and distrobox solve for GUI applications. One less reason to layer things.