Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
emilycook
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
31 ms
·
91.
▲
by
emilycook
7y ago
That's fair, I had the same experience coming from a lower COL area, and when I was interviewing I was able to negotiate for a higher salary and they adjusted. If GitLab wants you badly enough then they'll do what every company do
92.
▲
by
emilycook
7y ago
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.
93.
▲
by
emilycook
7y ago
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 wo
94.
▲
by
emilycook
7y ago
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 issue
95.
▲
by
emilycook
7y ago
https://about.gitlab.com/handbook/people-operations/global-c...
96.
▲
by
emilycook
7y ago
GitLab employee, that is indeed our goal: https://about.gitlab.com/handbook/product/single-application
97.
▲
by
emilycook
7y ago
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
98.
▲
by
emilycook
7y ago
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...
99.
▲
by
emilycook
7y ago
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
100.
▲
by
emilycook
7y ago
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 h
101.
▲
by
emilycook
7y ago
In case you're actually curious, we do publish our grafana stats here: https://dashboards.gitlab.com
102.
▲
by
emilycook
7y ago
Hi! We definitely don't run slowly this often, our dashboard is published here: https://dashboards.gitlab.com
103.
▲
by
emilycook
7y ago
> 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 par
104.
▲
by
emilycook
7y ago
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.
105.
▲
by
emilycook
7y ago
> 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
106.
▲
by
emilycook
7y ago
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
107.
▲
by
emilycook
7y ago
> 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 d
108.
▲
by
emilycook
7y ago
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 wo
109.
▲
by
emilycook
7y ago
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 t
110.
▲
by
emilycook
7y ago
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
111.
▲
by
emilycook
7y ago
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% p
112.
▲
by
emilycook
7y ago
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...
113.
▲
by
emilycook
7y ago
GitLab employee, actually our plan is to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy
114.
▲
by
emilycook
7y ago
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 backg
115.
▲
by
emilycook
7y ago
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/
116.
▲
by
emilycook
7y ago
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/
117.
▲
by
emilycook
7y ago
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/
118.
▲
by
emilycook
7y ago
GitLab employee, actually our plan is to go public by 2020. Our strategy page is public: https://about.gitlab.com/company/strategy
119.
▲
by
emilycook
7y ago
GitLab employee, nope! Our plan is to go public by November 18, 2020: https://about.gitlab.com/company/strategy/
120.
▲
by
emilycook
7y ago
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 commun
More ›