HNHacker News
TopNewBestAskShowJobs

emilycook

229 karma · joined November 15, 2018

Sr. Community Program Manager @ CircleCI
submissionscomments
emilycook··on Ask HN: Who is hiring? (May 2019)
Hi! GitLab employee here, thanks for your question. Someone from recruiting will be writing a more informative response to you by the end of the day. In the meantime, we have outlined some of the rationale behind this requirement here in this merge request: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... (and a little more discussion here: https://gitlab.com/gitlab-com/www-gitlab-com/issues/895)
emilycook··on The Remote Manifesto
> but with that kind of location based salary that pushes people to try and game the system. Get hired while saying you live in an expensive area and finally move somewhere cheap.

Doesn't this somewhat conflict with the idea that companies who pay local rates are going to discriminate against people who live in higher cost-of-living areas? Because if that's true, then yeah you could try to game the system by asking for a SF based salary, but the trade-off is that now you're less competitive. You'd have to be pretty confident that your skills were top-tier enough to offset that I guess.

emilycook··on The Remote Manifesto
Disclaimer, I am a GitLab employee. But IMO this isn't really comparing apples-to-apples, since we're specifically talking about remote companies. Sure, someone may have 2 job offers from 2 different remote companies, in which case the company offering SF rates has the advantage. But I'd argue that would be a fairly rare case overall given how globally competitive remote work is.

What's probably more likely is that someone is comparing Local Company A vs Remote Company B (this was my case), with the compensation rates being fairly equal. Then, the decision is "am I willing to be paid less than a coworker in SF for the opportunity to work remotely?" I was fine with that trade-off personally, and I'm sure a lot of people who are attracted to remote work would be as well.

emilycook··on Gitlab 11.10 Released
Hi! I've passed this on to our support team. Sorry for the inconvenience!
emilycook··on Gitlab 11.10 Released
No, thank you for using GitLab! We appreciate you :)
emilycook··on Gitlab 11.10 Released
Unfortunately I don't see this being a priority for us, as it would be a fairly large-scale operation for not a lot of benefit. However, you can open an issue for it here if you want! https://gitlab.com/gitlab-org/gitlab-ce/issues
emilycook··on Gitlab 11.10 Released
One option would be to add your most important stuff to the Operations Dashboard, since the button for it is always shown up top. You can also set it as your home page (Settings - Preferences - Default dashboard)
emilycook··on Gitlab 11.10 Released
It's not! :(
emilycook··on Gitlab 11.10 Released
Sorry to hear that! I've commented on your issue and will pass it along.
emilycook··on Gitlab 11.10 Released
I'm sorry you feel that way. There is a lot of thought that goes into our pricing and what tier a feature should go in. At the end of the day though, we still need to make money as a company. If you're interested in how we determine which tier something goes in, you can read about it here: https://about.gitlab.com/handbook/ceo/pricing/#the-likely-ty...
emilycook··on Gitlab 11.10 Released
Hmmm I'm not sure changing our whole naming system is feasible, but I mean, you can still call it whatever you want to I guess.
emilycook··on Gitlab 11.10 Released
I'll pass this along and see if we can provide an update. Thanks!
emilycook··on Gitlab 11.10 Released
Hi! Thanks for the feedback. I see that issue hasn't been commented on by us in a while, so I'll pass that on to our product team
emilycook··on Gitlab 11.10 Released
Hi! Thanks for the feedback. We'd love to be as lightweight as Gitea, but our end goal of being a single application for the entire DevOps lifecycle means that we are naturally more complicated. We are always working toward improving our resource usage though! You can see our issues around performance here: https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...
emilycook··on Gitlab 11.10 Released
You caught me, I'll pass this along to our product team. Thanks for the feedback!
emilycook··on Gitlab 11.10 Released
Hi! It is actively being worked on, but it didn't make it into this release. It is scheduled for the 11.11 release, and we don't foresee it being pushed back any further. Thanks for your feedback!
emilycook··on Gitlab 11.10 Released
Thanks for your feedback! We do have quite a few issues open to improve snippets that you can look at here: https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name=sn...

(although if you don't see an issue that asks for what you're wanting, I'd strongly suggest opening one so we can look into it)

emilycook··on Gitlab 11.10 Released
Community Advocate for GitLab here, thank you so much! We're working hard for y'all :)
emilycook··on Gitlab 11.10 Released
Ah, you've warmed my little GitLab employee heart. Thanks for your feedback!
emilycook··on CodeFlow: Improving the Code Review Process at Microsoft (2018)
Community Advocate for GitLab here. We can't share that data publicly (also because it's hard to track since many are on open source core), but we do have over 100k orgs using GitLab
emilycook··on Travis CI acquired by Idera
Disclaimer, I am a GitLab employee, but we have some docs on this that you can find here:

GitLab vs CircleCI: https://about.gitlab.com/devops-tools/circle-ci-vs-gitlab.ht...

GitLab vs TravisCI: https://about.gitlab.com/devops-tools/travis-ci-vs-gitlab.ht...

emilycook··on Travis CI acquired by Idera
GitLab is an LLC, GitHub is what's owned by MS
emilycook··on GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
Thank you! That was really helpful. Sometimes you just get so familiar with something that you lose focus on what it's like to view it for the first time, I'll pass along your feedback
emilycook··on GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
(GitLab employee) What would you say GitHub does that makes it easier to get started on/adopt? I don't disagree, barriers to entry are just subjective so I'd like to hear your take
emilycook··on Why We Chose Rails to Build Gitlab
(gitlab employee here) what is it you find particularly painful? It's definitely not intended to make it seem like people should go with hosted, so any feedback you have would be really appreciated
← PreviousPage 5 of 5