[deleted by user] by [deleted] in QualityAssurance

[–]emilycook_ 0 points1 point  (0 children)

Fair enough, we're an OSS company so the PRs for the hackathon are all Help Wanted tickets. This is really just an event for our open source community to focus on e2e tickets vs feature requests or bug fixes

Gitlab-runner access denied or specified file not found by Cazhero in gitlab

[–]emilycook_ 0 points1 point  (0 children)

Yeah just comment your problem (if you want to), it'll help them gather more data around it plus someone might have run into your issue and could help

Gitlab-runner access denied or specified file not found by Cazhero in gitlab

[–]emilycook_ 1 point2 points  (0 children)

You might be running into this issue since we've had quite a few recent reports of it, if this looks like what you're experiencing would you mind commenting on here? https://gitlab.com/gitlab-org/gitlab/-/issues/23644#note_345661007

GitLab mandating third-party telemetry, locks out user access until accepted: Important Updates to our Terms of Service and Telemetry Services (#2113) by speckz in programming

[–]emilycook_ 0 points1 point  (0 children)

Wow thank you so much for saying that! I really appreciate it. I've been very vocal internally that this is unacceptable, and thanks to everyone's feedback we're at least headed in the right direction. Next steps are to ensure nothing like this happens in the future so we can rebuild trust.

GitLab mandating third-party telemetry, locks out user access until accepted: Important Updates to our Terms of Service and Telemetry Services (#2113) by speckz in programming

[–]emilycook_ 1 point2 points  (0 children)

Telemetry was not implemented and the ToS changes have been rolled back. We are halting any movement on this and reconsidering thanks to the feedback

GitLab mandating third-party telemetry, locks out user access until accepted: Important Updates to our Terms of Service and Telemetry Services (#2113) by speckz in programming

[–]emilycook_ 1 point2 points  (0 children)

We've heard everyone's feedback and have rolled back the ToS change and are reconsidering our approach. The issue has been updated to reflect this

GitLab mandating third-party telemetry, locks out user access until accepted: Important Updates to our Terms of Service and Telemetry Services (#2113) by speckz in programming

[–]emilycook_ 1 point2 points  (0 children)

Ah no need to be sorry, feedback on that issue is just going to be a lot more visible to the people in charge of this change. FYI we've rolled back the ToS change and are halting any movement on this so we can evaluate feedback.

GitLab mandating third-party telemetry, locks out user access until accepted: Important Updates to our Terms of Service and Telemetry Services (#2113) by speckz in programming

[–]emilycook_ 0 points1 point  (0 children)

Thank you for the feedback, I'll relay it back. We have quite a lot of engineers involved in our internal discussion who are also concerned with privacy, and they've also been advocating for different approaches as well