4 ms·

from gitlab: https://gitlab.com/gitlab-org/gitlab/issues/34833#note_235154077 https://gitlab.com/gitlab-org/gitlab/issues/34833#note_23515... ----------------

by simpss 7y ago

from gitlab: https://gitlab.com/gitlab-org/gitlab/issues/34833#note_235154077 https://gitlab.com/gitlab-org/gitlab/issues/34833#note_23515... ------------------ We've heard your concerns and questions. There were many more concerns than we expected. We’re going to process the feedback and rethink our plan. We will not activate product usage tracking on GitLab.com or GitLab self-managed before we address the feedback and re-evaluate our plan. We will make sure to communicate our proposed changes prior to any changes to GitLab.com or self-managed instances, and give sufficient time for people to provide feedback for a new proposal. We'll work in this issue.[1] Here's an MR updating our blog post accordingly: gitlab-com/www-gitlab-com!33289 (diffs, comment 235139590)[2] ------------------------- 1 - https://gitlab.com/gitlab-com/www-gitlab-com/issues/5672 https://gitlab.com/gitlab-com/www-gitlab-com/issues/5672 2 - https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/33289/diffs#note_235139590 https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

jagged-chisel 7y ago
Did we get a reversion to the older ToS with this?
- simpss 7y ago
  no concrete answer regarding that yet. I don't think the new ToS was published on gitlab.com already, so this might not be necessary. I asked the question to get a clear answer, probably won't hear anything back regarding this. edit: ToS has been rolled back as well: https://gitlab.com/gitlab-org/gitlab/issues/34833#note_235221218 https://gitlab.com/gitlab-org/gitlab/issues/34833#note_23522...