HNHacker News
TopNewBestAskShowJobs

emilycook

229 karma · joined November 15, 2018

Sr. Community Program Manager @ CircleCI
submissionscomments
emilycook··on GitLab – A $1B business where all employees work remotely
Do you expect to scale up, and if so will you continue with this model? I took a look at your team page and you have 48 members, whereas GitLab is almost at 800.
emilycook··on GitLab – A $1B business where all employees work remotely
The best response to this that I can give is a link to our blog post about this, where we break down why we pay local rates:https://about.gitlab.com/2019/02/28/why-we-pay-local-rates/

So disclaimer, I work for GitLab. But the draw to working here isn't the possibility of making an SF salary, it's to work remotely for the same salary as working for a local company. I don't really care if I'm making less than a colleague in SF, because the benefit of working remotely while not taking a pay cut is already worth it. It's not for everyone though, so if you don't see working from home as a big enough benefit then that's valid.

emilycook··on Gitlab 12.1 Released
Summary of the release:

- The first iteration of Merge Trains [1] is released, allowing merges in the pipeline queue to run in parallel

- Merge requests for confidential issues [2]: there is now the ability to mark MRs on confidential issues as confidential, instead of having to work in a private repo

- Automated Let’s Encrypt certificates for GitLab Pages [3]

- Git object deduplication [4]

- Deploy Boards for Kubernetes clusters at the Group [5] and Instance [6] level

- Assigning groups as code owners [7]

[1] https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipeli...

[2] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...

[3] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...

[4] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...

[5] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...

[6] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...

[7] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...

emilycook··on GitLab – A $1B business where all employees work remotely
https://about.gitlab.com/handbook/people-operations/global-c...
emilycook··on Gitlab: 2019 Developer Report
GitLab employee, that is indeed our goal: https://about.gitlab.com/handbook/product/single-application
emilycook··on Gitlab is battling scalability issues
Hello! Just wanted to comment on this, since I'm a GitLab employee and my team is responsible. We currently only have 1 person who is able to do this (my team is 3 people but we all have our own focus areas), so when he's OoO they take a while to get renewed. But we're working on training up/getting access for the rest of the team and also potentially hiring someone else, so hopefully this can get crossed off your wishlist!
emilycook··on Degraded performance on GitLab.com
We haven't had any other reports of this, please submit a ticket here if you think there's an issue so we can track it: https://support.gitlab.com/hc/en-us/requests/new?ticket_form...
emilycook··on Degraded performance on GitLab.com
Gogs isn't exactly the same product though. If all you need is a git repo then sure, but it's all the other features that make GitLab more difficult to maintain
emilycook··on Degraded performance on GitLab.com
Hi GitLab employee, just gonna echo what the other person said and say that it isn't controversial to say that! We know that we don't work for every situation, if all you need is a repo, then by design we can't compete with how lightweight something like Gitea is.
emilycook··on Degraded performance on GitLab.com
In case you're actually curious, we do publish our grafana stats here: https://dashboards.gitlab.com
emilycook··on Degraded performance on GitLab.com
Hi! We definitely don't run slowly this often, our dashboard is published here: https://dashboards.gitlab.com
emilycook··on Oh shit, git (2016)
> I kind of wish GitLab would implement Mercurial support

Hi! GitLab employee here. Mercurial support has been a hot-ish topic internally. If you want to weigh in then please comment on this Issue, since Issue interaction plays a big part of how we prioritize https://gitlab.com/gitlab-org/gitlab-ce/issues/31600

(edit: I'm an idiot I should've read the full thread first since someone already linked it. gonna leave it up anyway)

emilycook··on GitLab Strategy
Yeah that's fair, and we're pretty aware that we don't have e.g. the social functions that GitHub has. Your comment has sparked some internal discussion though, a full integration would be interesting.
emilycook··on GitLab Strategy
> Are they profitable?

The goal is to go public by November 18, 2020. You can read all about it here: https://about.gitlab.com/company/strategy/

We have an MR open to mention our long term profitability target for Q4FY25 here: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

emilycook··on Ask HN: Why does Gitlab's top-right logo now say “Gitlab Next”?
The other commenter is right about canary testing. We have an issue open to make this more clear: https://gitlab.com/gitlab-org/gitlab-ce/issues/61503
emilycook··on GitLab Strategy
> 8. Every single open source project I use or contribute to uses github. If GitLab were to, say, add a github integration that lets me work with all the github repos I care about, but using Gitlab's UI, I would be intrigued.

This does exist: https://docs.gitlab.com/ee/user/project/import/github.html#m...

emilycook··on GitLab Strategy
GitLab employee here, who have you been talking to? Because that has 100% not been my experience working here. I live in a pretty middle-tier area, and I was offered a salary that was pretty much on-par with I was making at the company I worked for locally. My draw to GitLab wasn't the idea that I'd be making a SF level salary, it was (primarily, for me) the ability to work remotely. I couldn't really care less that I'm getting paid less than my colleagues in SF, because the ability to get paid the same amount that I would at a local company while working remotely was already worth it.
emilycook··on GitLab Strategy
That's definitely fair, and warrented. We haven't really had the resources for (relatively) long to put into performance when we were still in early stages. However we've constantly been improving that, to the point where I truly doubt you'd find that we suffer disproportionately from performance issues more than any competitor.

Before I worked here, I was on a team that evaluated different devops tools, and I felt the same apprehension about the uptime. But we eventually chose gitlab, and the only real downtime we experienced was during the 2017 outage. And we liked having the option to switch to self-hosted if it became too much of an issue

emilycook··on GitLab Strategy
GitLab employee, thank you for your kind words, and I also couldn't agree more! We're currently all at our company-wide conference [1], and legit every single employee is passionate about transparency (and also very happy to work here). Definitely not something I've experienced at the other companies I've worked for.

[1] https://about.gitlab.com/company/culture/contribute/

emilycook··on GitLab Strategy
GitLab employee, this is somewhat of a drawback to how transparent we are about our issues. I know this might seem like I'm just trying to PR spin it, but it's a real phenomenon. We post about any little problem we have, and 99% percent of our Issues are public, so it probably seems like we have a lot of downtime and problems because of how often we talk about them
emilycook··on Gitlab's Journey from Azure to GCP
Hi, employee from GitLab here. The move to GCP was planned before the Microsoft acquisition of GitHub was announced: https://gitlab.com/gitlab-com/migration/commit/ab5bf6b03ffc0...
emilycook··on Gitlab's Journey from Azure to GCP
GitLab employee, actually our plan is to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy
emilycook··on Gitlab's Journey from Azure to GCP
Hi, GitLab employee from "marketing" here. I take a little offense to

> Putting aside valid thing that article was written by person with role at gitlab 'Content Marketer'

A lot of us in marketing have technical backgrounds and are GitLab code contributors, that's what made us competitive for the positions we were hired for. We just write a lot of the blog posts so the product teams can focus on their own work. They're also usually very collaborative.

Sorry if you meant no offense, it's just a bit of a button-press issue for me!

emilycook··on Gitlab's Journey from Azure to GCP
Hi, GitLab employee! Don't worry, our plan is actually to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy/
emilycook··on Gitlab's Journey from Azure to GCP
Hi, GitLab employee! Don't worry, our plan is actually to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy/
emilycook··on Gitlab's Journey from Azure to GCP
Hi, GitLab employee! Don't worry, our plan is actually to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy/
emilycook··on Gitlab's Journey from Azure to GCP
GitLab employee, actually our plan is to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy
emilycook··on Gitlab's Journey from Azure to GCP
GitLab employee, nope! Our plan is to go public by November 18, 2020: https://about.gitlab.com/company/strategy/
emilycook··on Gitlab's Journey from Azure to GCP
GitLab marketing employee here, just popping in to say that a majority of us focus on both (and are encouraged to). While we aren't specifically on the "product" team, we're still code contributors like any other community member. That was one of the biggest perks for me joining a FOSS team.
emilycook··on Stripe’s fifth engineering hub is Remote
GitLab employee here, yes we do! I honestly couldn't go back to a company without asynchronous communication.

https://about.gitlab.com/handbook/communication/

← PreviousPage 4 of 5Next →