4 ms·

From the article: "Enterprise Edition (EE) No current changes. We are not adding telemetry services to EE at this time."

EpicEng 7y ago
>at this time Which was recently added after receiving a metric ton of backlash. You have to question their initial thought process here.
- kevin_b_er 7y ago
  Check out some more of the thought process: https://gitlab.com/gitlab-org/telemetry/issues/34 https://gitlab.com/gitlab-org/telemetry/issues/34 The original title was "Remove the ability to toggle sending telemetry data back to GitLab", then "Remove the ability for on-prem users to toggle sending telemetry data back to GitLab"
  - ArchReaper 7y ago
    That thread is disgusting. It's crazy how many people in that thread seem to be suits with no dev comprehension whatsoever, talking about shit that can tank the reputation of their company. >I'm not familiar with the term "dark patterns". Then you should not be suggesting changes like this in the first place. >I want to highlight again that public sector customers will be excluded from this. I've mentioned many times that it's important we respect their strict privacy requirements. But fuck private sector customers? What?
rossmohax 7y ago
EE excempt was just added, initial version of blog post implied that only CE would stay without tracking.
dorian-graph 7y ago
> We are not adding telemetry services to EE at this time. That sounds like something to rely on, especially given how they've handled this so far. Also, this wasn't originally there.
bobwaycott 7y ago
> We are not adding telemetry services to EE at this time. Emphasis mine, but the wording is notable.
kuschku 7y ago
That means nothing, if the owner of the instance has to sign a legal contract (which the ToS is) allowing Gitlab to track the data, then (a) the owner won’t upgrade, or (b) they owner becomes GDPR incompliant immediately.

4 ms·

From the article: "Enterprise Edition (EE) No current changes. We are not adding telemetry services to EE at this time."

by aetimmes 7y ago

EpicEng 7y ago
>at this time Which was recently added after receiving a metric ton of backlash. You have to question their initial thought process here.
- kevin_b_er 7y ago
  Check out some more of the thought process: https://gitlab.com/gitlab-org/telemetry/issues/34 https://gitlab.com/gitlab-org/telemetry/issues/34 The original title was "Remove the ability to toggle sending telemetry data back to GitLab", then "Remove the ability for on-prem users to toggle sending telemetry data back to GitLab"
  - ArchReaper 7y ago
    That thread is disgusting. It's crazy how many people in that thread seem to be suits with no dev comprehension whatsoever, talking about shit that can tank the reputation of their company. >I'm not familiar with the term "dark patterns". Then you should not be suggesting changes like this in the first place. >I want to highlight again that public sector customers will be excluded from this. I've mentioned many times that it's important we respect their strict privacy requirements. But fuck private sector customers? What?
rossmohax 7y ago
EE excempt was just added, initial version of blog post implied that only CE would stay without tracking.
dorian-graph 7y ago
> We are not adding telemetry services to EE at this time. That sounds like something to rely on, especially given how they've handled this so far. Also, this wasn't originally there.
bobwaycott 7y ago
> We are not adding telemetry services to EE at this time. Emphasis mine, but the wording is notable.
kuschku 7y ago
That means nothing, if the owner of the instance has to sign a legal contract (which the ToS is) allowing Gitlab to track the data, then (a) the owner won’t upgrade, or (b) they owner becomes GDPR incompliant immediately.