4 ms·

Please do revert, Sytse. Look at how governments are fighting Microsoft's urge to track users [0] [1] We're in the process of taking a 50user Premium (aka self

Please do revert, Sytse. Look at how governments are fighting Microsoft's urge to track users [0] [1] We're in the process of taking a 50user Premium (aka self-hosted) GitLab subscription, don't make us reconsider and search alternative means. [0] https://edps.europa.eu/press-publications/press-news/press-releases/2019/edps-investigation-it-contracts-stronger_en https://edps.europa.eu/press-publications/press-news/press-r... [1] https://tweakers.net/nieuws/158892/ https://tweakers.net/nieuws/158892/

sytse 7y ago
We're updating the blog post with https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33278/diffs https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
- simpss 7y ago
  as long as the ToS doesn't reflect a change of heart, this does nothing. In enterprise environments, we can't base anything on blog posts, it's the ToS that matters. ps: SOC2 does not inspire confidence as the whole of EAA needs to follow GDPR.
  - sytse 7y ago
    Thanks, we're pumping the breaks on this change completely, see https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33289/diffs https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
    - jahlove 7y ago
      > GitLab's proprietary Self-Managed packages (Starter, Premium, and Ultimate) are unchanged for now. We do plan to enable product usage tracking for those packages, but will absolutely allow administrators of self-hosted instances to have easy control over whether tracking is enabled. We will communicate clearly in advance of any planned changes, and will clearly document how to control tracking in each customer environment. This doesn't seem like you're pumping the breaks "completely". It's baffling to me that you would try to run telemetry on self-hosted PAYING customers. Seems totally backwards.
      - simpss 7y ago
        A while later, they did pump the breaks completely by reversing the ToS changes. This means they would have to change the ToS before trying to implement it again, which means the current result isn't moving the goalposts at all and is not a step forwards to the original solution. See: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33302 https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... and https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33308 https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

sytse 7y ago

We're updating the blog post with https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33278/diffs https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

simpss 7y ago
as long as the ToS doesn't reflect a change of heart, this does nothing. In enterprise environments, we can't base anything on blog posts, it's the ToS that matters. ps: SOC2 does not inspire confidence as the whole of EAA needs to follow GDPR.
- sytse 7y ago
  Thanks, we're pumping the breaks on this change completely, see https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33289/diffs https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
  - jahlove 7y ago
    > GitLab's proprietary Self-Managed packages (Starter, Premium, and Ultimate) are unchanged for now. We do plan to enable product usage tracking for those packages, but will absolutely allow administrators of self-hosted instances to have easy control over whether tracking is enabled. We will communicate clearly in advance of any planned changes, and will clearly document how to control tracking in each customer environment. This doesn't seem like you're pumping the breaks "completely". It's baffling to me that you would try to run telemetry on self-hosted PAYING customers. Seems totally backwards.
    - simpss 7y ago
      A while later, they did pump the breaks completely by reversing the ToS changes. This means they would have to change the ToS before trying to implement it again, which means the current result isn't moving the goalposts at all and is not a step forwards to the original solution. See: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33302 https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... and https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33308 https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...