5 ms·
The issue I see it that Linux distributions generally build software from source on their own CI. This means that their telemetry data won't reflect Linux users
by hashhar 5y ago
The issue I see it that Linux distributions generally build software from source on their own CI. This means that their telemetry data won't reflect Linux users habits and hence be useless at best or detrimental in the worst case to the decisions made using said incomplete telemetry.
- merb 5y ago> If you are compiling Audacity from source, we will provide a CMake option to enable the telemetry code. This option will be turned off by default.
- hashhar 5y agoDistributions will disable telemetry by default. e.g. Debian etc. Only individuals running from-source OS or package managers will be able to enable telemetry.
- capableweb 5y agoMy guess is that Linux users (or users who use package managers in general) are happy to provide bug reports or even patches when they find bugs. Less can be said about users downloading the binaries directly from Audacity's website (Windows and macOS users), which I'm guessing is a fair bit of share. Those users will still get the choice to enable telemetry or not, and I guess those are the most important to get the telemetry from, as they are not as happy to provide bug reports nor patches.
- hashhar 5y agoThat a very valid point. But the sad truth is that if the people in charge of deciding product direction are the people looking at telemetry instead of bug reports/patches from users then in the end the Linux user's interests will not be high up (or even visible) to the product direction decider. I've seen this happen before at some previous workplaces where the telemetry and analytics was the only factor controlling decisions - and this lead to the vocal (but not visible in telemetry) userbase getting the short end of the stick on many occasions.