emilycook

9 ms·

31.
by emilycook 7y ago
We have been taking the feedback seriously, we rolled back our ToS changes and are reconsidering our approach here. More info can be found on the issue
32.
by emilycook 7y ago
(GitLab employee however these are my personal views) I agree that our blog posts about competitors aren't great (and thankfully have been happening less), but for this issue I'm glad to see that the backlash has been taken seriou
33.
by emilycook 7y ago
GitLab employee, some employees have proposed this idea and (speaking personally) I think it would be a better approach. We've halted movement on using telemetry and are reconsidering. More info is on this issue: https://git
34.
by emilycook 7y ago
We're halting any movement on this and reconsidering our decision on telemetry, you can find more information here: https://gitlab.com/gitlab-org/growth/product/issues/164
35.
by emilycook 7y ago
The ToS was the only thing that had changed, telemetry had not been implemented yet. We've rolled the ToS changes back and are reconsidering our approach based on the feedback: https://gitlab.com/gitlab-org/growth&
36.
by emilycook 7y ago
We've rolled back the ToS update and had not implemented telemetry yet, we're reconsidering our plan based on the feedback. More info and further discussion can be found here: https://gitlab.com/gitlab-org/gr
37.
by emilycook 7y ago
I don't know what that means, but this is the handbook page on my position: https://about.gitlab.com/handbook/marketing/community-relati... although I've been needing to update it a bit. My job is to bas
38.
by emilycook 7y ago
Work at GitLab, we've halted any movement on adding telemetry and are reconsidering our approach. More info is on this issue: https://gitlab.com/gitlab-org/growth/product/issues/164
39.
by emilycook 7y ago
Trust me I understand, I was a developer prior to this job, but I do think this is necessary information to clarify what the blog post itself said. As the person who relays everyone's feedback to the rest of the company, I am listening
40.
by emilycook 7y ago
I hope I covered that in my other comment
41.
by emilycook 7y ago
I was just trying to make a joke I'm so sorry. As for recaptcha we have an issue here with a ton of discussion around it that links quite a few more if you're interested: https://gitlab.com/gitlab-org/gitlab-f
42.
by emilycook 7y ago
I'm so sorry I was trying to make a joke, it's been a long day as the messenger trying to relay everyone's concerns about this back to our team.
43.
by emilycook 7y ago
Hello! Self-hosted users on EE are currently not affected, we opened an issue here to clarify: https://gitlab.com/gitlab-org/growth/product/issues/164
44.
by emilycook 7y ago
edit: was trying to make a joke, it was a bad joke
45.
by emilycook 7y ago
We're testing this out on .com to see what value it really gives us and how it works, and depending on that then we might roll this out to EE. HOWEVER any move to do so will be properly communicated, and we're not going to impleme
46.
by emilycook 7y ago
This is the issue they were talking about, I hope it clarifies some things! https://gitlab.com/gitlab-org/growth/product/issues/164
47.
by emilycook 7y ago
Hello! We're sorry for the confusion, we opened an issue here that might help clear things up. Feel free to voice any concerns or feedback there so it can be properly relayed back: https://gitlab.com/gitlab-org/gro
48.
by emilycook 7y ago
Hello! We opened an issue here including a section on why we made this change: https://gitlab.com/gitlab-org/growth/product/issues/164
49.
by emilycook 7y ago
Hello! We're sorry for the confusion, self-hosted EE users are not affected by this change. We opened an issue here to clarify: https://gitlab.com/gitlab-org/growth/product/issues/164
50.
by emilycook 7y ago
Hello! Thanks for your feedback, because of it we added a section on our new issue about why we're doing this: https://gitlab.com/gitlab-org/growth/product/issues/164
51.
by emilycook 7y ago
Hello! We're sorry for the confusion however EE is unaffected by this. We wrote an issue here to clarify: https://gitlab.com/gitlab-org/growth/product/issues/164
52.
by emilycook 7y ago
Hello! Thanks for the feedback, we opened an issue here that might help clear some of this up: https://gitlab.com/gitlab-org/growth/product/issues/164
53.
by emilycook 7y ago
Hello! GitLab employee, I understand the frustration however from what I can tell from your usecase you will not be affected. We opened an issue here to help clarify: https://gitlab.com/gitlab-org/growth/product&#x
54.
by emilycook 7y ago
Hello! GitLab employee, I understand the frustration however self-hosted customers on EE will not be affected. We opened an issue here to help clarify: https://gitlab.com/gitlab-org/growth/product/issues/
55.
by emilycook 7y ago
Hi! GitLab employee here. We understand this is a topic that you all are concerned about, so we opened an issue to help clarify [1]. If you have any comments or concerns you’d like to relay back to us, you can do so there! We appreciate the
56.
by emilycook 7y ago
The specific plan is to stay independent: https://about.gitlab.com/company/strategy/#goals
57.
by emilycook 7y ago
GitLab employee, our plan is to go public by next year: https://about.gitlab.com/handbook/being-a-public-company/
58.
by emilycook 7y ago
Hi GitLab employee, I can assure you we won't sell out, Sid our CEO is very adamant about going public in 2020 and we're currently on track (actually ahead of it wooo) https://about.gitlab.com/handbook/being
59.
by emilycook 7y ago
Sorry if you find this spammy! It's huge news for us and we all (of course lol) have a vested interest in making sure the company succeeds. Since we don't have Microsoft funding to enable us to throw resources at everything in our
60.
by emilycook 7y ago
Hello, GitLab employee. I definitely hope we've matured a lot since 6 years ago! In early 2015 there were still only 9 employees [1] compared to almost 900 now. [1] https://about.gitlab.com/company/history/

More ›