Yesterday, GitLab retracted its earlier decision to implement user level product usage tracking on their websites after receiving negative feedback from its users.
Hello! We've heard the feedback and are reconsidering our decision on this. Right now any movement on this has been halted and our TOS rolled back. More discussion around it can be found here: https://t.co/yNJxrQ9Nth
— GitLab (@gitlab) October 24, 2019
GitLab.com users were specifically notified that until they accept the new service terms condition, their access to the web interface and API will be blocked. This meant that users with integration to the API will experience a brief pause of service, until the new terms are accepted by signing in to the web interface. The self-managed users, on the other hand, were apprised that they can continue to use the free software GitLab Core without any changes.
The DevOps coding platform says that SaaS telemetry products are important tools to understand the analytics on user behaviour inside web-based applications. According to the company, these additional user information will help in increasing their website speed and also enrich user experience.
Following this announcement, GitLab received loads of negative feedback from users.
Any recommendations for a good SaaS issue tracker/bug reporter?
(not gitlab, b/c telemetry)
(not github, b/c ICE)
— Andy Hunt (@PragmaticAndy) October 24, 2019
are you serious to start including an user tracker in both your public https://t.co/QmzNjW9Fm3 hosting AND in all (non open-source) customers' installations?
This is a serious blow to user privacy.#gitlab
— Cr0ydon (@Cr0ydon) October 24, 2019
what happens if you give too much vc money to people? they sell out to 3rd party tracking non-sense. i feel like the male-shit-up marketing industry hasn’t heard the shot. @gitlab officially peaked. downhill from now on i guess. @dhh pic.twitter.com/XQXf54PXZv
— BlindMyStare (@BlindMyStare) October 24, 2019
@gitlab Bye forever! A few more weeks and I'd have bought into Enterprise, but now, screw it. You 100% don't need telemetry to "make GitLab better faster," and we don't need GitLab.
— Chance (@TheChanceSays) October 23, 2019
Although, GitLab has rolled backed the Telemetry service changes for now, and are re-considering their decision, many users are warning them to drop the idea completely.
Nice to see @gitlab actually listen to the backlash and roll back the changes regarding the telemetry so far. However, as their update mentions, they are rethinking their approach to this same idea. Keep an eye on upcoming changes that bring this back in any manner.
— atom0s (@atom0s) October 24, 2019
@gitlab I strongly suggest you take the community’s feedback seriously and drop all plans to add telemetry to GitLab. You’ve already done unrepairable damage to your reputation, and for now I will no longer recommend GitLab to others.
— Ryan Rule-Hoffman (@ry60003333) October 25, 2019
Gitlab tried to backdoor its product with nasty telemetry à la windows 10, but as we can see users don't want to be ripped of from their data. Privacy invasion is an unacceptable behavior that should be opt-…https://t.co/A0jazxdv91 https://t.co/zbJf3VH4H1
— tresronours cybersec (@tresronours) October 25, 2019