3 ms·

So first of all I’d recommend you try to understand your users. Your EE users use your self-hosted product because they don’t want anything leaving their premi

So first of all I’d recommend you try to understand your users. Your EE users use your self-hosted product because they don’t want anything leaving their premises — not a single bit of data. If you require this, do you really think EA, SIEMENS, Ericsson, Lockheed Martin or Bayer are going to let any data from their instances with potentially secret and internal future projects leak out to you or your third parties? No, they won’t. They’ll require you signing a contract that you won’t track them, or they’ll switch vendors — you’re the small fish in that case. Additionally, I’d suggest reading and understanding the GDPR — the text is actually surprisingly simple: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679&from=EN https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL... So you, or in case of the EE Edition, your customers, have to have explicit, clear, and freely given[1] consent to allow any telemetry or tracking which contains PII to happen at all, and especially to give any PII to third parties. Pseudonymous data counts as PII. Data which contains the IP (such as a direct connection to a third-party server to transmit data) counts as PII. [1] Even more interesting, freely given consent is defined as explicitly opt-in, and it has to be in clear and simple language, the default (and/or the biggest button) has to be rejecting everything, and the consent can not lead to any functional changes, so you can’t require opt-in to let the user access any functionality either.

aetimmes 7y ago
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.

aetimmes 7y ago

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.