HNHacker News
TopNewBestAskShowJobs

emilycook

229 karma · joined November 15, 2018

Sr. Community Program Manager @ CircleCI
submissionscomments
emilycook··on Gitlab ‘rethinking’ third-party telemetry
(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 seriously because I had my own concerns. It'd be much more worrying if this went forward despite all of the imo justified backlash.
emilycook··on Gitlab ‘rethinking’ third-party telemetry
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://gitlab.com/gitlab-org/growth/product/issues/164
emilycook··on Gitlab ‘rethinking’ third-party telemetry
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
emilycook··on Gitlab ‘rethinking’ third-party telemetry
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/product/issues/164
emilycook··on Gitlab ‘rethinking’ third-party telemetry
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/growth/product/issues/164
emilycook··on Gitlab ‘rethinking’ third-party telemetry
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 basically relay feedback to the rest of the company, and relay any information back to you all that might be relevant. We don't wanna be out-of-touch with what people are really saying about us, and we wanna make sure you're input is received, so that's basically why my team exists.
emilycook··on Gitlab ‘rethinking’ third-party telemetry
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
emilycook··on Update on free software and telemetry
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, which is why this new issue was created in the first place. Thank you to everyone who provided feedback, I am doing my best to advocate for you.
emilycook··on Update on free software and telemetry
I hope I covered that in my other comment
emilycook··on Update on free software and telemetry
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-foss/issues/46548
emilycook··on Update on free software and telemetry
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.
emilycook··on Update on free software and telemetry
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
emilycook··on Update on free software and telemetry
edit: was trying to make a joke, it was a bad joke
emilycook··on Update on free software and telemetry
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 implement it without carefully considering an appropriate opt-out strategy.
emilycook··on Update on free software and telemetry
This is the issue they were talking about, I hope it clarifies some things! https://gitlab.com/gitlab-org/growth/product/issues/164
emilycook··on Update on free software and telemetry
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/growth/product/issues/164
emilycook··on Update on free software and telemetry
Hello! We opened an issue here including a section on why we made this change: https://gitlab.com/gitlab-org/growth/product/issues/164
emilycook··on Update on free software and telemetry
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
emilycook··on Update on free software and telemetry
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
emilycook··on Update on free software and telemetry
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
emilycook··on Update on free software and telemetry
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
emilycook··on Update on free software and telemetry
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/issues/164
emilycook··on Update on free software and telemetry
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/164
emilycook··on Update on free software and telemetry
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 feedback and want to be as transparent and accommodating as possible.

[1] https://gitlab.com/gitlab-org/growth/product/issues/164

emilycook··on KDE is adopting GitLab
The specific plan is to stay independent: https://about.gitlab.com/company/strategy/#goals
emilycook··on KDE is adopting GitLab
GitLab employee, our plan is to go public by next year: https://about.gitlab.com/handbook/being-a-public-company/
emilycook··on Macron Secures €5B Investment to Boost French Tech Startups
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-a-public-company/

Also FYI, Sid is Dutch but we're registered in the US, although our entire company is remote :)

emilycook··on Gitlab More Than Doubles Valuation to $2.75B Ahead of Planned 2020 IPO
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 backlog, we rely heavily on user experience to help us prioritize. Which just so happens to come up much more organically on sites where devs are more empowered to voice their opinions freely :)
emilycook··on Gitlab More Than Doubles Valuation to $2.75B Ahead of Planned 2020 IPO
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/

emilycook··on Gitlab More Than Doubles Valuation to $2.75B Ahead of Planned 2020 IPO
Hi, GitLab employee here. Sorry to hear that! This funding should enable us to throw more resources at maturing some of our features (e.g. we tripled our employee count this year). We spun up this product maturity page to make this a little more transparent: https://about.gitlab.com/direction/maturity/
← PreviousPage 2 of 5Next →