Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab acquires Gitter, will open-source the code

venturebeat.com

Post reply on HN
Print view View original

311–320 of 333 posts

Re: GitLab acquires Gitter, will open-source the code

#311

Post by jsudhams »

onion2k wrote: post #307
stonith wrote: post #261

Earlier quoted context omitted.

Access to talent in locations where there aren't offices + access to talent who only work remotely.

So you seem to think a Bay Area company should pay it's remote workers Bay Area money. That'd be lovely, but we should explore what it infers. Let's assume that Gitlab will open a Mumbai office in a month's time. Would you expect the people there to get typical Mumbai wages, or typical Bay Area wages? Assuming you don't think it's Bay Area wages (because that's crazy), why do you think going to an office in your loca…

Some of us get Bay Area salary in hyderabad and bangalore. Why should we not get bay area salary when we deliver the same or better. I have no control over my cost of living but i do control what i will work for. No matter where.

Re: GitLab acquires Gitter, will open-source the code

#312

Post by Arathorn »

systemfreund wrote: post #119

When it's going to be open sourced then we could finally implement a proper matrix.org bridge. Currently all messages are relayed through a special gitter user called matrixbot

matrix-appservice-gitter actually supports 'puppeting' already - letting you log in as your own user. But native Matrix support for Gitter would be incredible!

Re: GitLab acquires Gitter, will open-source the code

#313

Post by sandGorgon »

suprememoocow wrote: post #300
sandGorgon wrote: post #163

Earlier quoted context omitted.

No - because, like discord, gitter makes it a point to make privacy very hard to set up. This is fairly deliberate and is the reason why enterprises have a hard time adopting it.

Sandeep, it's interesting that you view it that way, but it was never our intention to deliberately make privacy hard. When creating a new room, you can choose to make it public, private and optionally allow anyone from your GitHub org to join your private room. See http://imgur.com/jIb8EKA It's definitely true that the product focus on Gitter has always been more on public rooms. That's because the focus of our comp…

I completely understand and respect that. It was not a complaint - but cognizance that you had a certain philosophy in mind.

Forget slack - look at hipchat which has far simpler privacy controls. The ability to create an organization (NOT linked to GitHub), per channel permissions is all that's needed. Hipchat makes this dead simple.

Lots of different people will have different requirements - some people will need Active Directory even, but essentially the only two things needed for enterprise messaging is permissions and search.

Re: GitLab acquires Gitter, will open-source the code

#314

Post by yellowapple »

webo wrote: post #129
hamandcheese wrote: post #110

Somewhat off topic, but I was once very interested in working for GitLab. According to their compensation calculator, though, I'd be making less than half what I make now (also working remotely). They ding me for living in a comparatively low cost area. I'm surprised they are able to attract talent to achieve what they have done so far. It makes me worry somewhat about my future prospects in an increasingly globalize…

Senior Backend Engineer shows 85-95k in Chicago, which is below average. It shows 45-55k for Fayetteville -- most junior guys/gals start around 75k in Fayetteville at mediocre companies.

Same deal in Sacramento; it'd be more cost-effective (even factoring in time and cost of transportation) to just commute to the Bay Area, which quite a few people already do.

Re: GitLab acquires Gitter, will open-source the code

#315

Post by it33 »

slg wrote: post #22

Does anyone have an insight into the differences between Slack, Mattermost, and Gitter? I have only ever used Slack before but it seems like Gitlab is already heavily invested with Mattermost. That makes me wonder what the future looks like for both Mattermost and Gitter. Are they different enough that they can both coexist without hurting either product or is one of them destined to be folded into the other in hopes…

Mattermost is for self-hosted communication. E.g. automated deploy to your cloud account, etc.: https://www.youtube.com/watch?v=AKqHWqrAgpk&t=83s

Here's a blog post on differences with Mattermost and Slack: https://www.mattermost.org/what-slack-might-learn-from-its-o...

Re: GitLab acquires Gitter, will open-source the code

#316

Post by mikekchar »

taude wrote: post #310
mikekchar wrote: post #259

Earlier quoted context omitted.

I've worked in several jobs where I've thought, "If I'm going to have to put up with this BS, they're going to have to pay me a lot more". And the funny thing is, often times they are willing to pay you more if you ask. So there have been times in my career where I've been miserable pretty much exactly because I decided to work in a really stressful environment while accepting a large salary. As I get older, I'm not…

At what point do you discount your skills so much that you can't afford to save for kid's education, retirements savings, etc, though. In looking at those GitLab pay scales, it's a pretty SEVERE pay cut for all but the most junior people. I'm not sure I'd be comfortable with a 50% pay cut to do "something cool".

From Wikipedia: The U.S. Census Bureau reported in September 2016 that real median household income was $55,775 in 2015.

If you scroll down to education and look at the chart for education, you will see that the median household income for someone with a bachelor's degree is $68,728. With a professional degree (like a P.Eng) it's up to $100K.

Can you afford to save for your kid's education, retirement savings, etc on the median household income in the US? That depends a lot on your lifestyle. It certainly is possible.

I'm not going to tell you what's good for you. I'm just saying that there are people (myself included) who can live comfortably on less and who value things other than money when accepting a job. I was simply answering the question that was asked: How is it possible to hire quality people while paying below market rate? By making it worth the reduction in pay. Whether or not Gitlab succeeds in doing this, I have no idea.

Re: GitLab acquires Gitter, will open-source the code

#317

Post by bartread »

developer2 wrote: post #279
sashagitlab wrote: post #171

Earlier quoted context omitted.

Hi Matt, I am the recruiter at GL, I've reviewed your case, and I wanted to follow up personally. I'd like to address your concern and explain our process. Since the time of your interview, we have changed the process of discussing compensation within the first 15 minutes of a conversation to the end of a phone call. We understand it's uncomfortable and sometimes awkward to talk pay when you've just met someone. Hope…

Holy crap, you've just done your company - or if you are an external recruiter, your client - a huge disservice by posting this reply. You've done nothing to assuage future candidates' concerns. You've merely confirmed that your compensation offers, and likely the entire hiring process, is driven by undesirable corporate metrics. This makes GitLab sounds seem like a company that only knows how to regurgitate HR 101 t…

Speaking from the candidate's perspective, I tend to avoid companies where money is discussed upfront. I want to be able to demonstrate the value I can add, and then have a negotiation about remuneration based on that value.

Bluntly, yes, it does put the candidate in a much stronger negotiating position but, hey, if you really want to hire good people then I'm afraid it's hard cheese. Conversely talking about remuneration upfront puts the candidate on the back foot because there's substantially less of a basis for convincing negotiation, so it really becomes about cutting costs for the company.

Unless you absolutely have to - sometimes you might not have any other option, and you shouldn't let pride blind you to that reality when you're facing it - I'd always recommend you avoid working for anyone where you've had to discuss money first.

Re: GitLab acquires Gitter, will open-source the code

#318

Post by anonymous_green »

hamandcheese wrote: post #110

Somewhat off topic, but I was once very interested in working for GitLab. According to their compensation calculator, though, I'd be making less than half what I make now (also working remotely). They ding me for living in a comparatively low cost area. I'm surprised they are able to attract talent to achieve what they have done so far. It makes me worry somewhat about my future prospects in an increasingly globalize…

This is quite common they like to brand themselves as startup and remote company with all their slimy tactics to pay their employees below market rate. I've had their team deny the proof that the salary expectation I asked for is with-in the normal range even if they are a remote company and a startup.

Nobody should be paid as low as 50-60k per annum when they expect people to perform same as someone paid 90-120k. Here are some of the links where I raised this point as well:

https://news.ycombinator.com/item?id=13549948 https://news.ycombinator.com/item?id=10924957

This link suggests their average salaries to be 115k but their calculator is just for people who they'd like to scam into paying below par.

https://www.indeed.com/salaries/Gitlab-Salaries

Re: GitLab acquires Gitter, will open-source the code

#319

Post by anonymous_green »

sytse wrote: post #47
orb_yt wrote: post #42

Earlier quoted context omitted.

Looks like they will open source the whole thing. I'd be very interested in learning how much Gitlab paid for this acquisition.

I'm sorry but we don't comment on acquisitions prices. Being transparent about it is not common in the industry and us doing this by default might make future acquisitions harder since the company being acquired might not like it. Also see https://about.gitlab.com/handbook/general-guidelines/ "Most things are public unless there is a reason not to. Not public by default are: financial and legal information"

..because financials is something people hope a company to be more open. It takes quite alot of courage to honestly reveal all the salaries. Then you wouldn't need a calculator anymore. So probably you should consider when you are acquiring talent, talent may set the price based on their own needs and have a right to negotiate. You shouldn't first of all, build an annoyingly outdated calculator and give it to HR to reject good talent and rely on community to mess up when the decision to build that calculator was mostly to serve company's own purpose. (which probably why its more biased to downpaying employees)

Re: GitLab acquires Gitter, will open-source the code

#320

Post by therealmarv »

jobvandervoort wrote: post #114
therealmarv wrote: post #97

Earlier quoted context omitted.

Generally I have the opinion that the CI of gitlab is much more powerful because of real Docker usage (and also works on private repos for free). Speaking about the gitlab CI... why is there no status or statistics page about it on status.gitlab.com and why is a new build pending over 30 minutes currently (now) ?

You can find some public monitoring regarding CI on GitLab.com here [0]. I agree that we should have some status on CI as well, made an issue [1]. [0]: http://monitor.gitlab.net/dashboard/db/ci [1]: https://gitlab.com/gitlab-com/infrastructure/issues/1360

Wow that gitlab monitor on [0] looks really great. Thanks! Can I ask which software that is? :)
Post reply on HN