Hacker News Reader

Comment by Aeolun | Hacker News Reader

Wow! That’s some change to just drop on us. Guess that settles the issue of whether or not we’re ever going to be able to use this in the enterprise with a big fat no.

I’m not really sure why they’re thinking this is a good idea.

If I tell the legal team that our source control software is sending off data to the vendor and some random (unspecified?) third parties, they’ll have a fit.

View on HN

yeah, it's interesting: i figured that Lab always targeted/understood "enterprise" more than Hub, what with Hub's focus on more social type stuff (activity feeds etc.) and Lab always having a nice matrix of tiers that, while expensive, weren't prohibitive for enterprise users + foot in the door with self hosted

i wonder if their projections for enterprise aren't adding up, or Hub has started to eat their lunch enterprise wise with new features that Lab hasn't copied yet, or API integrations, or something else

Except... A lot of enterprises use github enterprise, which I would imagine has similar telemetry? I don't actually know so perhaps I'm wrong...

I mean, you're not wrong necessarily, but some people specifically chose gitlab because it was _not_ being hosted elsewhere or harvesting data.

Choice is good, more things like this mean that there's less of a differentiating factor between hub and lab.

Hello, GitLabber here! We’re currently writing an issue explaining the situation, once it’s public I will link it here.

I think we as developers understand the rationale behind it. The outrage you may see is that in self hosted instances, the companies and people that pick that as their option do so because they want an isolated/independent system. Telemetry from a self hosted system is atypical, especially compared to SaaS that's hosted by you. It's more normal in apps people download that already use the internet, but you already have that option in what you host.

Frankly, I used to work at a DoD contractor and we ran GitHub Enterprise and GitLab behind secured networks. That kind of expectation -- that the software will never phone home -- was what let us run and justify them in the first place.

Edit: Looks like the comment I replied to has been changed, and essentially removed. I'm sorry if this is now out of context.

"Until the new Terms are accepted access to the web interface and API will be blocked. So, for users who have integrations with our API this will cause a brief pause..."

It's not even take it or leave it, one has to agree first in order to leave.

It seems whoever approved this, forgot why people arrived to GitLab from GitHub.

It's not that we do not understand that, we do, it's that we don't agree with such stupid and aggressive move considering enterprise setups (I certainly will not use this version if I can avoid it). Shame, this is exactly the opposite of why I migrated to Gitlab.

This is the issue they were talking about, I hope it clarifies some things! https://gitlab.com/gitlab-org/growth/product/issues/164

Not really, as you will see from the first user comment.

Hello! GitLab employee, I understand the frustration however from what I can tell from your usecase you will not be affected. We opened an issue here to help clarify: https://gitlab.com/gitlab-org/growth/product/issues/164

I would prefer not to see GitLab employees all over this thread on every comment like those PR folks on Twitter.

Let people speak, and listen.

Trust me I understand, I was a developer prior to this job, but I do think this is necessary information to clarify what the blog post itself said. As the person who relays everyone's feedback to the rest of the company, I am listening, which is why this new issue was created in the first place. Thank you to everyone who provided feedback, I am doing my best to advocate for you.

I don’t understand why an ‘issue’ was created for this. It means absolutely nothing to me that there is an issue when the original blog post still blatantly announces that the next version of Gitlab Enterprise is going to exfiltrate our company data.

While I’m here. You also keep talking about opt-out functionality, but the only way this is going to go over reasonably well is if the whole thing is opt-in.

Reply on news.ycombinator.com