229 karma · joined November 15, 2018
and the relevant epic: https://gitlab.com/groups/gitlab-org/-/epics/915
> when you look at the team list in Gitlab, it shows everyone who has access to the team
This has been an ongoing issue for a while, but a fix is currently scheduled for 12.4: https://gitlab.com/gitlab-org/gitlab-foss/issues/44958
> server squashing commits
You don't have to provide a custom squash message, and the default behavior will be either (a) taken from the first multi-line commit message in the merge, or (b) the merge request’s title if no multi-line commit message is found.
Documentation: https://docs.gitlab.com/ee/user/project/merge_requests/squas...
The original issue around this: https://gitlab.com/gitlab-org/gitlab-foss/issues/47149
But yeah my team (of 3 members lol) was spun up primarily because Sid our CEO wants to make sure that everyone in the company is plugged into what users are saying about us, and he cares about hackernews specifically since GitLab was founded here [1]. So my team mainly just triages mentions about us so devs/managers/etc don't miss feedback but can still focus on their jobs. I do see first-hand that everyone in the company really does care about what people are experiencing.
[1] https://about.gitlab.com/company/history/#2012-gitlabcom
[1] (in case you care at all about my job description lol) https://about.gitlab.com/handbook/marketing/community-relati...
---
[1] (same link as #2 above) https://about.gitlab.com/handbook/engineering/development/en...
[2] https://about.gitlab.com/handbook/engineering/performance/
[1] https://about.gitlab.com/handbook/being-a-public-company/
As per your second point, and this is speaking personally and not really officially, I do think our feature goal has been historically a bit too ambitious (although hopefully transparently so: https://about.gitlab.com/company/strategy/#breadth-over-dept...) seeing as how we're barely out of the startup phase. But we have had a big hiring push this year and have almost tripled our headcount (which did introduce growing pains of it's own lol). Once we've stablilized a bit, we will be able to dedicate more resources solely on maturing features.
I hope this doesn't come across like making excuses, these are just my observations as a user-turned-employee. I will take your feedback about not being heard into consideration though so we can improve on that!
The gender pay gap is a whole separate matter that I'd prefer not to get into because, tbh, talking about it in tech-spheres that are still male-dominated is intimidating. I guess all I can say beyond this is that if you're ethically against these practices then I support you voicing that, and while I can offer differing opinions, I still think you're within your right to openly disagree.
Because there really aren't that many of them, and even fewer who aren't also using local rates.
> Living in a cheap area comes with drawbacks.
I agree, I live in a cheaper COL location. But, I was already living here, so I'm not sure how my salary at GitLab affects that. Local companies don't pay you more because of the drawbacks of living in a cheaper location. If I moved to a higher COL location then I would be compensated for that [1]. The mechanics are the same, I just get to do my job from home.
> I’d care a lot if I made a lot less than a colleague for the same type of work at the same company
This is, I think, the most important factor. I didn't decline my offer at GitLab in favor of staying at my previous company because I knew my salary would be the same as every other employee. I compromised on that front so I could work remotely for a company that I really felt like was a better fit for me.
[1] https://about.gitlab.com/handbook/people-operations/global-c...
To be frank, I don't think the gap in skill between the top-top-top tier employees and those who are competitive candidates for non-SF salary remote positions is all that wide, nor do I think it's necessary for a company's success to only hire the absolute pinnacle of talent. We're also not competing in the same consumer market as many SV startups, so if a different remote company has a higher saturation of top-tier developers, I'm not sure why that affects us unless they're a competitor.
I do see this point though, and I'm sure Sid does as well, but the level of skill that the people I work with have vs the employees at my previous (local) company is incomparable. Everyone is very good at what they do, and are motivated to continue working here because of all of the other perks of working for a company like GitLab.