Hacker News Reader

Comment by btasovac | Hacker News Reader

Hello all, GitLabber here!

We opened an issue for gathering feedback at https://gitlab.com/gitlab-org/growth/product/issues/164 and you can find the most up to date information regarding this topic there. Please join the discussion and let us know what you think.

View on HN

You say "discussion", but many of the Gitlab developer comments in that thread consist of the same response copy-and-pasted verbatim in response to multiple different people, which comes across more as PR spin than as a good-faith attempt to engage in a discussion.

Why would there be a “discussion”? They knew their users didn’t want this anti-feature before they implemented it and they did it anyway.

Then they add insult to injury by pretending to “discuss” it as if user consent or participation has anything to do with this.

We have been taking the feedback seriously, we rolled back our ToS changes and are reconsidering our approach here. More info can be found on the issue

I don't believe that requiring explicit agreement to a new ToS before being able to access account deletion is kosher.

The ToS have been rolled back, and telemetry had not been implemented yet. I (of course) don't want anyone to leave, but hopefully that alleviates any concerns if people want to.

This entire thread kept me up last night. Revisiting it this morning, there's a ton of well expressed, clear, opinions and facts here in this discussion. On the other hand, the amount of information expressed in the issue, does not nearly contain enough of what's in this HN thread.

Good morning. If you commented yesterday, express your product needs for zero telemetry and trust here: https://gitlab.com/gitlab-com/www-gitlab-com/issues/5672

(GitLab employee... of course) Sorry this thread kept you up (no sarcasm). If it helps at all, I'm responding to you right now because I'm here gathering all of the feedback, since there was so much discussion on here/reddit/twitter/the issues that need consolidating. I'll be making a lot of noise so the people in charge can truly see the impact this had

Please have your co-workers stop spamming the same comments in every HN thread about Gitlab's poor decision.

I realize this is also spammy, my bad, but I do wanna clarify that it's explicitly our job to respond to questions/concerns and relay feedback to the company: https://about.gitlab.com/handbook/marketing/community-relati...

I'm going to be honest: I don't care that it's your job. Don't do it.

I'm not looking forward to GitLab "taking into account" the community comments, then ignoring them and forging ahead with this change.

Reply on news.ycombinator.com