News for hackers. Stuff that matters.
Re:Thanks Gitlab by sytse on Thursday October 24, 2019 @12:59PM (#21346540)
We also called out our signups at GitLab when GitHub got acquired, so it is more than fair that Drew is posting this.

BTW As Drew said https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... we're pumping the brakes on the telemetry changes.

Re:Thanks Gitlab by 0x8BADF00D on Thursday October 24, 2019 @01:11PM (#21346697)
I got an email from you guys yesterday and I have to say I was quite confused. My company is an EE customer and we pay for our seats. Why are you including this telemetry? For the free version I understand, but you should not be treating your enterprise customers like this.
Re:Thanks Gitlab by sytse on Thursday October 24, 2019 @05:14PM (#21349256)
I'm sorry our plans were so far off the mark.
Re:Thanks Gitlab by protomikron on Thursday October 24, 2019 @01:02PM (#21346585)
> [...] we're pumping the brakes on the telemetry changes

So you revert (don't implement it)? Thx! Reverting it is the right decision (I hope that means "pumping the brakes").

Re:Thanks Gitlab by esotericn on Thursday October 24, 2019 @01:10PM (#21346682)
From what I can tell they're still going to do it, but in a different way, e.g. it might be opt in (hopefully not in a fake-opt-in style like a GDPR popup) or opt out or whatever.

Fundamentally they want to do telemetry it seems and are trying to figure out a hack to get people to accept it.

Re:Thanks Gitlab by emilycook on Thursday October 24, 2019 @03:59PM (#21348580)
(GitLab employee) we're discussing other options too, I'm personally advocating strongly against just going ahead with the current plan. My preference would be for no third-party involvement and just better ways to analyze the data we already have
Re:Thanks Gitlab by acrispino on Thursday October 24, 2019 @01:38PM (#21347045)
Pump the brakes? No. Reverse course, before your product ends up in the same place as github.