You can read Gitter’s post: http://blog.gitter.im/2017/03/15/gitter-gitlab-acquisition/
And here is what VentureBeat had to say about the news: http://venturebeat.com/2017/03/15/gitlab-acquires-software-c...
UPDATE: and here is GitLab’s post with a few more details: https://about.gitlab.com/2017/03/15/gitter-acquisition/
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 globalized talent pool.
Edit: Didn't intend to make a scene or put anyone on blast here. Just thought the calculator was a little silly. Thanks for the responses gitlab staff.
It seems to me the issue is more there was a difference in expectations between what the candidate perceived was their situation and what the recruiter believed. This is of course not uncommon, however from the sounds of it the candidate was not given an opportunity to reason their position. It could be that GitLab is simply not offering competitive renumeration based on what the candidate believed they could achieve in the same market. It could also be that GitLab undervalued the particular skill sets of the candidate. Of course the opposite may also be true.
Clearly there were differences in opinions, however by asking the candidate to sign an agreement to a specific salary based on no discussion is only going to cause issues for everyone. Either the candidate agrees, goes through the interview and decides "it's not worth it, and now there's no flexibility", they disagree and a potentially good candidate is immediately lost or they agree, take the job and feel like they are not being fairly compensated, which can have all sorts of consequences.
This is usually why the discussion happens at the end of an interview process, after the candidate has had the opportunity to demonstrate their skills and experience. Then if there is still a perception of a mismatch this can be reasoned with respect to what has previously been discussed.
> Secondly, we never would ask you to agree to something that is below the calculators suggestion, however your expectations based on Level, Experience, or Location may differ from the recruiter or hiring managers' assessments.
The candidate has clearly stated they were offered less than what the calculator suggested. It was your recruiters opinion that they did not meet the parameters entered into the calculator, however clearly the candidate believed that they did. In this case the recruiter must judge the cause of the disparity through discussion with the candidate and set expectations in terms of the results of this discussion. Again, simply telling a candidate "this is our opinion, you must agree to it" is not going to benefit anyone.
Matt, since I deal with the comp calculator every now and then, if you'd like to provide more specifics of your situation, can you please email me on email@example.com ?
We have to decline 200 applicants a week at GitLab. We realize that interviewing is very stressful. We send a survey afterwards to get a net promoter score. The current average is 4.2 out of 5 for people that did not sign with us. Most applicants don't fill out the survey, we're not sure how that influences results.
Your data-source for this is very clearly wrong.. any income/cost-of-living report for India will show that the cost of living is the same for these 2 cities.
GitLab, diversify/improve your recruitment strategy. Why you only have "the recruiter", aka a single person heading your recruitment, rather than a group of competent personnel, is concerning. Your public image is of a medium-sized company which is already established, not a tiny startup outfit wherein all hires rely on a sole (apparently inadequate) person vetting each potential employee.
There are multiple people involved in the hiring process here at GitLab, specifically several people who handle phone screens and resumes. The responsibility of vetting doesn't rest solely on one person and is actually a pretty collaborative process in my experience. As an example, I was able to vet every single candidate's resume myself for roles I was involved in hiring for.
Either way, the parent comment is full of language that raises red flags to competent developers. Personally, my first thought is "oh hell no!". It's possible that their comment is not representative of the company's effective policies, but when one perceives this kind of reply as an official stance of the company's standpoint, it is difficult to retract.
The way I understood it, at least, was 'the recruiter who handled the interview with "matthewvincent"'. Doesn't imply that there are, or are not, other recruiters at gitlab.
And if so, at least to me it seems honest for said recruiter to come forwards personally, instead of some feel-good mumbo-jumbo from the PR department.
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.
It really is that basic. When the company cares more about the money than what the employee can bring, they've shown their company cares more about their internal politics then they do about their future success. Simple as that.
What if you hire a great remote developer who lives in San-Jose, then she moves to Kentucky 6 months later, and their contribution is still the same. Why should their pay be adjusted?
> Are software companies pricing their computer programs based on location? Do folks in Ohio get to pay less than folks in New York?
This is the sentiment I usually see but how are one's expenses or expected living standard is relevant regarding compensation for work? Imo it is very hard to argue against equal work => equal pay. At least from a moral pov.
Btw that is a lot of incorrect assumptions about expenses, including where someone's children might want to go to college, globally fixed costs like work equipment and cloud services, not to mention goods which are actually cheaper in the US.
Since when? I'm pretty sure I've never seen any variation in software prices except international variances, which are most often a case of with/without tax and currency fluctuations.
> > Are software companies pricing their computer programs based on location? Do folks in Ohio get to pay less than folks in New York?
No. If I understood that, I wouldn't have replied as I did, would I now?
> go on with replying that you still think it's wrong to base the compensation on the location's living expenses
But why is it a location's living expenses? If a company is paying people to work remotely, location should have zero impact on remuneration: they aren't asking you to live anywhere specific, so there is no business reason to use location as a cost factor.
Why is that a requirement? Do you somehow think the Bay Area has a monopoly on good developers?
If a person wants to work for the company but their offered salary isn't high enough to sustain a high cost of living environment, the person will need to either move or find another job.
The company has literally the entire world to find staff - that's the whole point of remote workers.
GitLab claims to be "Remote Only": https://about.gitlab.com/jobs/
We have a 'headquarters', which is also where Sytse (CEO) lives, where there are a number of desks available for special occasions, but no one is ever required to work from a particular place.
> Why does Location matter? Does it matter if have 10 kids, or a lease on a Porsche, or 2 alimonies, or live in a McMansion, or my kid has cancer? Are those factors relevant? What makes Location special?
PS it is not about GitLab, I like their service (even better than GitHub) and it is great they are transparent about compensations. IMO if they were to eliminate location from their calculator they could get the cream of a very big talent pool.
I had an interview with Parsely a few years back. Took over 3 weeks of back & forth before they rejected me with a reason that should have been squashed the first hour of the interview.
Cynical read: We discovered people are more likely to compromise on the salary if they've already committed their time to the interview.
If you have any more information you can share, it'd be great if you could send it to peopleops at gitlab.com.
Interestingly issues gets noticed here!, there was a posting yesterday about FB hiring issue.
I'm familiar with how compensation is determined at Mozilla, and we use something similar but with different inputs. GitLab seems to be using rents as their determiner with New York as a baseline, which means way underpaying people in most markets. If they adjusted those numbers by the average percentage of income applied to rent (I believe a readily available number) then the numbers might be more reasonable.
At Mozilla we have a smaller number of regions, I think it's each nation plus three tiers in the U.S.: Bay Area/New York, Chicago/Seattle (not sure what all is in this bucket), and the rest of the country. Then we get data from some company that provides us with market rates for different given titles. We target salaries at the top 25th percentile (not a 25% bump like GitLab).
So given a title, people's compensation is figured as somewhere between 0.8x and 1.2x that market rate, depending where you are in your career. Each level bump is about 1.2x the previous level. So typically you might enter a Senior Engineer role at maybe 0.85x the compensation, and as you grow into the role you get to 1.0, and as you are approaching the next level you get into the 1.1s.
I think it's a pretty fair process. Especially internationally you can't relate salaries to each other well given different labor laws and taxes. Assuming our input numbers are right, our compensation is by definition competitive across markets – though in practice all sorts of weird things can happen over an employment history, like when a person moves.
All that said, it's clear we get a better value from people in cheaper markets, even while those people in practice also get a better value in terms of compensation. So far that hasn't been met with any adjustment in compensation, but instead some acknowledgement of the dynamic during recruitment.
But yeah, the outcome, remoters from Cheaptown effectively subsidizing their coworkers from Glitter City is incredibly ugly. One should at least hope that the decisionmaking processes at the employer do not completely isolate the one deciding on a hire from the cost difference, so that flyover guy could at least enjoy an increased chance of getting the job.
Finding something that applies to both (Or in this case something that works in neither, which makes it even clearer) is not the same as treating both as requiring the same solutions.
You want your cake and to eat it too?
Assuming you don't think it's Bay Area wages (because that's crazy), why do you think going to an office in your location means you ought to be paid a lot less?
I appreciate the openness from GitLab on this matter though, they're pretty up-front about it so if you don't like it don't apply.
 When the word "cost of living" is mentioned but it's not reflected in the price for final users then you know you're about to get fucked.
And the listed salary for my geo is about 2/3 to 3/4 of my current base pay before any bonuses. The idea of the company sounds good, but the pay is a deal breaker for me. I wouldn't like feeling like I'm providing the company more value but because the person lives in San Francisco they get twice as much pay. Maybe that is me being petty?
(Their calculator also seems somewhat bonkers (on the extremely low side) compared to the local market where I live. It seems based on a somewhat-arbitrary, quick-and-dirty-wild-guess estimate formula vs what real, on-the-ground competitor companies in those areas are paying.)
EDIT: there seems to be a small trend emerging where every company I've seen with fully-public payscales/pay calculators wildly comes in below what I'm currently making, and what I've heard from local competitors. And I'm not in SF. Wonder if there's some causality there, though it's still just a handful.
Also it's amusing to get a downvote for offering up the info that Gitlab would want me to take a pretty substantial ~30% haircut in base pay based on where I live. What would be attractive to me would be "we'll give you 80% of your current take-home, but you get to live wherever you want," but this is basically the opposite.
Seems backwards to have such a large incentive to live somewhere more expensive.
A lead (maximum seniority), with high (maximum) experience, in Fayetteville, AR makes less than most junior developers (60k-68k)...
 I've found this calculator to be decently accurate http://www.bankrate.com/calculators/savings/moving-cost-of-l...
It seems obvious to me that they should be paying relatively more to people in cheap locations than expensive ones. That saves Gitlab money, biases their hiring to people in cheaper areas, incentivizes people to move to cheaper areas, helps cool down the overheated housing markets in expensive areas.
I can see drawbacks to paying a strict flat amount regardless of local cost of living; some adjustments probably make sense. But Gitlab seems to be doing the opposite. I don't get it.
For example, when I lived in England, the difference between rent for a room in a shared house outside city center and a 1 bedroom apartment in the city center was usually at most 100% (excluding the very top and very bottom of the ranges). Meanwhile in Lithuania, where I live at the moment, the difference is about 6 times. You can't capture this in a calculator with such broad coverage.
Approach by mozilla (https://news.ycombinator.com/item?id=13881004) seems much more reasonable to me, to be honest.
Most likely, one of their founders is technically adept, there are a small number of other experienced people onboard because they incidentally live in areas where the compensation calculator doesn't screw them, and most others are riding on those coattails.
GitLab is really a sad story of lost potential. Most of the time, you can't fix these kinds of problems, because they start at the top and flow down (and you usually can't replace the top). A well-engineered GitLab alternative would be welcome.
What I see is an brilliantly managed company despite having a globally distributed team, which has a great pace of development, which is carving a nice market share in an extremely tough market (developers) and against a fierce competitor (Github), let alone the other multibillion company backed Bitbucket.
And their radical transparency, as you put it, is a fascinating thing in and of itself. If anything it makes me feel intimate with the company. Hard to put it in words, maybe because I was a rather early adopter but if you follow them closely it's a like you're there on their board with spectator mode on. That's some invaluable experience for HN crowd.
Are we even talking about the same company?!
The radical transparency may be a fun experiment and it may provide a lot of interesting data to parse, but it's not a good way to run a real company. It screams of impractical idealism. A lot of companies are bad, but GitLab wants to make sure that you know they're bad from a distance. In theory this is all great and nice. In practice, it hurts the company in both commerce and recruiting.
How do you get "brilliantly managed company" when they just had a massive data loss? How can you say that honestly?
My boss makes sure I backup stuff...and we're not taking on millions of dollars in funding and customers.
When you have an inexperienced crew running your tech, you get a lot of very preventable issues, which sometimes approach apocalyptic scale (like GitLab's February data loss). That's fine for some businesses, but it shouldn't be fine for something as important as GitLab.
So what if a smart experienced developer (their CTO) is able to get good prices on what he/she wants done through remote work? The point you're making is negativity for no reason without evidence on how it's not working, i.e. what's wrong with their product.
Other than that, GitLab is a beast to install and navigate and it requires a lot of resources. Rails is slow. The UI is weird (frequently end up not finding the repo I want due to the way the "trending" tab works). There are other issues. I'm not a GitLab contributor so I don't really have more technical detail, I just use it sometimes.
It seems like you're just assuming they're a great company with a well-engineered product because you like the corporate image they project.
I don't know of anything about them that makes either themselves or their product "amazing". It is somewhat usable, which is good; I'm not trying to besmirch the earnest efforts of people to make something that works, and indeed there are some uses for something like GitLab. That doesn't mean that GitLab is "amazing" or that their product is flawless or even good.
The most exciting thing about GitLab to me is remotely distributed teams, which I usually love seeing, but I think they've gone about it all wrong.
Your reflexive defense isn't any more useful than extreme criticism.
"All the things you said could be true, yet their product [could be] amazing."
Grammatically, it's called "elliptical." I then immediately say: "I haven't used it, but I like what I'm seeing"--so what I meant should be quite obvious.
What value are you adding with your criticism of what--in my case--at least has a question:
"What's actually wrong with the product? Why is it not 'well-engineered'?"
My point was extremely clear--his post needed to have evidence of how their processes results in bad product. And I asked that as a question--perhaps you know? Something tells me you even do (perhaps you're a Gitlab user), yet you're choosing to take an unproductive meta route of criticizing my partial criticism with no actual goal. What do you expect to accomplish with that?
I presume you got stuck on one word ("amazing"), made up your mind and didn't read the rest. My bad, i could have been more clear. However, the essence of what I was saying was straightforward, but you chose to see the forrest instead of the trees. A common reason people take that route is because there is something else you wished to express, but didn't--perhaps you have real experience with gitlab in one way or another that resonates more with the person's viewpoint I replied to. I'm not saying he's wrong--I just would like to hear the full reasoning behind that perspective.
I'd love to hear what that actual perspective is. Gitlab is an interesting product I haven't spent much time reviewing until today. Maybe you can provide the evidence to back up the original poster's point??
I haven't used it, but I like what I'm seeing
If you're just talking about what you're seeing, you have the same vantage point as everyone else and the original poster made a number of obvious and valid criticisms - data loss is one, they are selling software and a service.
It probably is trolling on my part, but as harsh as the original poster's words were, he's got some points.
I guess we have one bullet point, do we have more?
Just to throw my example in, they would want to pay me at least 20% less than what I currently make -- and I'm already a 100% remote employee working for a financially stable startup. What they offer is simply not even close to market value -- yet they claim it is. In this case it's the D.C. area.
As I get older, I'm not really that interested in putting up with the BS. So if I work in an environment without the BS, or if I have a boss who is willing to shield me from the BS, I'm very happy to pay for it.
Actually, there are tons of things I'll pay for. Remote working on a team that knows how to do it and respects remote workers? That's a big discount. A work process that allows me to work effectively in a different timezone or with flexible hours? Another discount. Guarantee that the work I'm doing will be released with a free software license? HUGE discount (really, huge). Working with interesting and talented people? Yep, discount. No inventions agreement? DISCOUNT.
You get the picture. Hell, I'll do a fair amount of work for free if you tick all the boxes. I'm nowhere near alone in this.
Edit: grammar... :-P
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".
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.
Top end salaries will still be discounted, naturally, because the costs in high cost areas are real. But not every scales like housing.
Living in Seattle, WA, the salary range I used topped out at ~$120k. However, 30 miles south in Tacoma it tops out at at ~$80k. Moving to Dallas would move the top of the range to ~$105k (Hot Market Adjustment?! but not Seattle?!).
Values I used (I rounded the salary up too):
* Above Average Experience
* United States
* Dallas, Seattle and Tacoma.
I'm looking to move to the Dallas area (from Tacoma) and my rent will likely end up being less in Dallas (at least 20%).
One thing that I thought was strange was the quiz/test at the end of each interview. I get that you want to make sure that the candidate has an adequate skill level, but I have a lot of open-source projects (hosted in GL), and I am (one of many people) horrible at live quizzes. Mostly because of nerves, being in an interview is stressful enough. The fact that I had to take a 30-45min quiz instead of going over my own code is not ideal. I just don't believe in standardized testing being a good measure to someone's ability. But, I really thought they were nice about it, and I wish them luck.
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:
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.
BTW Our compensation principles can be found at https://about.gitlab.com/handbook/people-operations/global-c...
Edit: and yeah, I've read a lot about your company including that link. I understand your approach, it just excludes me.
For U.S. it may be best to establish a floor, and for most cities don't go below that... Remote work in the U.S. tends to be closer to 65-75% of Northern California pay, from what I've seen. Often more than local rates, but harder to come by the jobs.
Also: we, digital nomads, don't have any base. I honestly have no answer to "where do you live"
Anyway I've looked at my homecity in Ukraine and salaries proposed are around 80-90th percentile (~$50k for senior developer).
The thing is there's no reason for a person to hold onto Gitlab. Once you get some remote experience there're a lot of companies who provide EU/US salaries even if you happen to live in Eastern Europe.
This is the one area, I'm quite interested in seeing how things play out, from a human resources point of view. Since GitLab is so transparent, it'll be interesting to see, if they publish any information on employee turnover in the future. Or any mitigation strategies they may develop, to help retain high value employees.
I applied to Gitlab, but then I noticed the calculator. London is below market rate. In Warsaw is half what Google pays.
Edits: typos, wrote from phone.
Still, good luck to them :-)
Some people (say, big companies) think exactly the opposite because they are after an on-prem solution, and for that Gitlab kicks Github's ass.
Ouch. If you run your own servers already it's financially worth hosting your own gitlab at the minimum price point.
I expect it will be the big orgs who don't move due to integration costs.
That said, I think it's always worth considering using a tool because of their options for the open-source community... github, travis-ci etc have changed the way a lot of people work. GitLab might be what I reach for for self-hosting, but more likely to try the community/open edition first.
Using VSO (VisualStudio.com) for hosting at work, and some of the integration parts are very nice... Though no idea what a private TFS instance costs.
They did a manual Backup before meddling with stuff so they only lost data from a really small timeframe.
CI downtime, on the other hand, is troublesome. I love using Gitlab CI and it didn't take me more than a few minutes to manually deploy what I had to, but I decided I need most of my CI to be controlled by me.
The end result is a simple refactor of my test and deploy specs to their own rake tasks (Could be Bash scriots or whatever) and I'll have Gitlab run a simple gle command, if it goes down I run the command manually...
Now some eventual downtime is not such a deal breaker anymore, and I continue having private repos and CI (Awesome CI) for even the smallest (And private) projects I work on... Not a bad deal if I do say so myself.
GitLab Enterprise Starter is $39/user/year, and GitLab Enterprise Premium is $199/user/year.
$21 is per-month. Per-year that works out to $250/user. If we're going by the month, GitLab's pricing is $3.25/user.
Mozilla does this to great effect:
This doesn't show all the graphs we need to show like 99th percentile request latency but that will come when we add Unicorn support to Prometheus.
It does need to be paired with something that can capture and display the NetFlow data well. But with that, you can literally see what data is going where in your network, accurate to the byte. And with a good visualisation solution, you have the data historically too, so you can (easily) match things up time wise.
eg a developer writes a bad query which pulls 1/2 the database over the network to the front end server for filtering results there, instead of filtering them in the database. You can see that on the network fairly easily, and let the developer self-educate (if given access to the tools). ;)
As an aside, the gold standard used to be a commercial product called "NetFlow Tracker". It was amazing (fond memories), but the company behind it (Fluke Networks) didn't seem to know anything about software sales. So, it's now discontinued. :(
Hopefully there's a modern version of that somewhere. :)
If you would like to follow progress you can dive into it all here . One of the spearpoints is Gitaly, which should significantly improve git access.
For everything else, I like Gitlab a lot -- it seems to have the best integration of tools of any code host.
I'm also warming to the idea of treating CI as "pipelines", and find myself thinking of tooling more in that way.
I love the integrated CI, though, and the use cases it enables. I love that I can just make a pipeline that lints, tests and compiles my code and then, if all of those pass, ends with deploying it to production.
There are many more Gitlab features I like a lot, and the fact that they're all integrated is icing on the cake.
Can't we be realistic about companies instead of getting wild eyed? You don't have any reservations about recent events?
I haven't seen them promoting that hard as you describe.
I wrote my comment of the pure satisfaction with their services and my use case. So stop being ignorant and be civilized and at least argument what you say. What happened to them month ago was an accident that could happen to many others, but the difference was that they were 100% open about it, with others you may won't even know shit is happening.
Nobody forces you to use anything.
Edit: And now you edit and delete 90% of comment, nice.
(My comment excludes the CI part)
I have. I've installed Gitlab and Mattermost on my own server. Gitlab is great but I found Slack was a better product (over Mattermost). Have you tried installing it?
I created a Gitlab account and was planning on using it over Github but their recent data loss scared me off. Is that unreasonable? It worries me just as much to see them buying a company a month after that. Is slowing down unreasonable?
I want to use Gitlab. I like their open approach, but if people just praise them without being objective about it it doesn't benefit any of us. I might just be a selfish and/or entitled user but you'll forgive me for wanting Gitlab to be good. Don't you?
No, please tell me how you installed a Slack server! (j/k, but it's also kind of the point: GitLab wins on-prem)
Mattermost team here, would welcome any feedback on how we could improve.
Here's a demo of Mattermost features vs Slack as FYI: https://www.youtube.com/watch?v=AKqHWqrAgpk
I had some confusion with the install. It seems the Docker install is favored, but not using a lot of Docker stuff I went with the gitlab-omnibus install on Ubuntu 16.10.
It worked but I didn't feel especially comfortable with it, there were a number of steps. That's vague enough be useless and it could have just been my own ignorance. What is the suggested install if that isn't too basic of a question?
I also had issues with it not liking users sending rather large files but I believe that's an odd use case.
I would use it again but the simplicity of Slack (no setup and no management) won out for now.
"What about Mattermost, how is this different?
Gitter was built to be used in the open. We’ve always seen Gitter as a network, or a place where people can come to connect to one another. Team collaboration, whilst possible, has never been a core aspect of the Gitter experience.
Mattermost is a powerful, integrated messaging product for team collaboration - we will continue to ship and recommend using Mattermost for internal team communication."
They surely have the best intentions. Hopefully one product doesn't take priority over the other and/or they can prevent cannibalization. There's definite overlap.
However, the service (gitlab.com) is constantly having issues, most of them not reported on their status page or on their twitter status account. For the last week it's been practically unusable, to the point where our whole dev team combined has wasted almost a hundred hours just re-trying builds and deployment jobs. Yesterday we tried, unsuccessfully, moving to the new AWS tools (CodeCommit, CodeBuild and CodePipeline), and today we just moved back to Bitbucket + CircleCI (we use RoR if you are wondering).
Unfortunately today I couldn't seriously recommend gitlab.com to anyone needing a reliable hosted repo + CI solution (maybe self-hosted works better though, YMMV).
Regardless, I have a deep respect for what Gitlab as a company has done so far. After looking into repo + CI options I've realized that they've created probably the best all-in-one platform out there, at least their vision/concept. Wish them the best and hope to use their service again in the near future once they have their stuff together.
> However, the service (gitlab.com) is constantly having issues, most of
> them not reported on their status page or on their twitter status account.
> For the last week it's been practically unusable, to the point where our
> whole dev team combined has wasted almost a hundred hours just re-trying
> builds and deployment jobs.
Jobs getting stuck might not seem like a big deal, but when every dev on the team needs to manually check every 5 minutes to make sure things are running and retrying everything, while clients are waiting on a hotfix, bugfix or a new feature that we promised we would ship by a certain deadline, then the issue becomes critical.
Cloud anything just seems like begging for this kind of problem.
Keeping even just one server secure and up to date is no small task. Additionally, in this particular case, given Gitlab pushes changes pretty often, we wanted to have access to the latest stuff without having to update the self-hosted instance every time (with the added risk of screwing up in the process). I guess there's a trade off for everything.
But seriously - people are willing to throw money for an enterprise gitter - especially after https://medium.freecodecamp.com/so-yeah-we-tried-slack-and-w...
Look at the number of people begging Discord to take money from them - https://feedback.discordapp.com/forums/326712-discord-dream-...
gitter always had search working - discord just got it recently.
Do you know of any enterprises using Gitter?
It's definitely true that the product focus on Gitter has always been more on public rooms. That's because the focus of our company has always been on the network of public communities, rather than enterprise features, which we feel are well represented in the market by other great products like Slack, Mattermost, etc.
(Background: I'm CTO/Cofounder at Gitter)
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.
(disclaimer: work at Discord & fishing for feedback about how we can make this easier)
I linked to a ticket - if you follow that trail, there are many more.
EDIT: Previously said open source, open core is the correct term.
Gitlab is incredible... but I really cant host right now. Same for mattermost.
I do believe that the ability to run a fairly large hosted system at scale and with incredible performance is what the gitter guys bring to the table.
Isn't that just Slack?
The Gitlab folks really know how to do it. It is of course the rational approach to it, but still, that's a bold move.
I tried Tower when it was in beta for Windows, but the cost is too steep to justify it for me. But it seemed to be a lot more full featured than the GitHub client which isn't good for more than basic commits. And again, no Linux there either.
I'd definitely go for a solid, open source git client, and it's obviously very relevant to GitLab's business.
You can actually use GitHub Desktop with any repo: https://help.github.com/desktop/faq/articles/do-you-support-...
(Although it looks like you have to clone it first?)
Seriously, SublimeText, which is $70 closed-source.
Less seriously, macOS and iLife. I'd be ok to pay €200/year/user for an OS of that quality, as long as it's open-source.
Not all of it. version.gitlab.com is one of GitLab's closed source IPs.
We do want to open source it when we can.
More details can be found on the developer site: https://developer.gitter.im/docs/faye-endpoint
We also have an open-source IRC bridge: https://github.com/gitterHQ/irc-bridge
Source? First time I hear that, and it seems unlikely, since they have quite a few features that don't fit nicely in stock IRC.
Here's a blog post on differences with Mattermost and Slack: https://www.mattermost.org/what-slack-might-learn-from-its-o...
Link to the live post: http://blog.gitter.im/2017/03/15/gitter-gitlab-acquisition/
"Even public companies"? Public companies are required to report a lot of financial information publicly that non-public companies are neither required to report nor in the habit of reporting.
The omission or misstatement of an item in a ﬁnancial report is material if, in the light of surrounding circumstances, the magnitude of the item is such that it is probable that the judgment of a reasonable person relying upon the report would have been changed or inﬂuenced by the inclusion or correction of the item.
In practice, a company's auditors will set a materiality threshold based on a company's revenue, assets, and net income. Thus, big companies can make small acquisitions without disclosing much.'
> What about Mattermost, how is this different?
> Gitter was built to be used in the open. We’ve always seen Gitter as a network, or a place where people can come to connect to one another. Team collaboration, whilst possible, has never been a core aspect of the Gitter experience.
> Mattermost is a powerful, integrated messaging product for team collaboration - we will continue to ship and recommend using Mattermost for internal team communication.
Surely GitLab would be better off investing fully into a single chat-platform? The road to making Gitter good for internal team communication is not particularly long or windy.
This is good though because mattermost is open-source only on paper. They refuse to integrate important features even when people contribute code (to protect their commercial version).
Third, people see GitLab as GitHub competitor. But really it competes with Atlassian.
First, we love GitLab. While we'd be flattered with an offer to join them, Mattermost has its own mission and motivation (https://www.mattermost.org/why-we-made-mattermost-an-open-so...)
Second, regarding community contributions, we have an open and transparent process for proposing, discussing and vetting contributions before a pull request is made (https://docs.mattermost.com/developer/contribution-guide.htm...).
When people don't follow the guidelines, and when they work hard to contribute something before engaging with the broader community--especially when it totally works but can't be officially accepted--we feel terrible.
Recent example: https://github.com/mattermost/platform/pull/5718
Previous related example: https://github.com/mattermost/platform/pull/2718
You can follow the links there to go into detailed, heated discussions around this in our own Mattermost instance.
In our manifesto, we lay out the purpose of the open source Mattermost Team Edition, and about the commercial Enterprise Edition (https://www.mattermost.org/manifesto/), and--at least in my mind--our decisions are based on scope (What purpose does X serve? Where should it belong, if at all)?
Our contribution guidelines are in our docs, they're in our developer docs, they're displayed to contributors before they can submit a merge request, and yet with the size of our community, we still have mistakes and awkward threads.
I hope we can do better here. If anyone would like to discuss, you're welcome to join our community server: https://pre-release.mattermost.com/
Third, yes, agree, GitLab is certainly competing with Atlassian, and winning a lot.
I wish project maintainers would stick to a network like freenode and just occupy a channel there dedicated to the project. I'm already set-up to take part in discussions there, I don't need to use a web browser etc.
Also I'm salty that most of these Slack-like services have no ignore feature/minimal moderation tools which are both things I've leaned on heavily when working with communities. That's probably a rant for another day, but it's related to why I really dislike using some of these things.
This might just be my perception, but it seems like most people I come across in this field were on IRC at some point.
This is what pushed me away from using Slack with a group of gamers I admin for. I can understand Slack's desire to stick to the workplace and how that leads to "if you need to /ignore a co-worker your company has problems implementing /ignore in Slack can't fix." And I can understand Mattermost wanting to become the opensource/on-prem analog of that. But it really falls apart when you try to use that kind of system with users that don't know you, aren't on your payroll or have issues with rules - like open source developers, or gamers.
My group eventually switched to Discord for, among other things, its amazing ACL-style permissions system, frictionless inviting and unlimited history (iirc, getting history with the first tier of paid Slack would have cost us ~11k USD/year?). It's not perfect - I really hope their bot API gets some love, and of course the ability to host your own server would be nice (though I understand some of the catch-22's there) - but I like it a LOT and I keep encountering new groups of people with Discord servers where I can just idle using one client. This is MUCH more IRC-like experience than I ever got with Slack (for instance, switching between or getting/setting notification alert levels on several different servers is much more ergonomic on Discord than on Slack).
I've not used Gitter a whole lot - just a couple of times when I had a question for some project that had one - but my impression is that it leans more towards "chat with strangers about $topic" (like Discord) and less towards "chat with colleagues about work" (like Slack). In that respect, I'd lay a small amount of money that Gitter does have an /ignore command, among other tools that you miss from IRC.
Not trying to be snarky. Maybe it was a typo, but non-English speakers might not immediately get from that to the correct word.
I've been helping some early coders in the FreeCodeCamp Gitter and have been impressed with the quality of the app for a company with little capital. They have done a lot with short resources.
It would be better in my opinion for small Slack communities to transition to Gitter since Slack has said they do not plan to support large scale free communities in the long term.
It's one of the few reasons why I am still using Github :( .
I would prefer if Gitlab CI was a separate product but there probably isn't a lot of benefit for Gitlab to do that. If you want to have Gitlab CI job results displayed in your Github branches you could try this test service:
Isn't there a "but sadly I don't love its CI" missing from the middle of this? Why is Travis the problem?
TravisCI for instance, is easily replaced in all of my projects with Gitlab's integrated CI.
I agree that we should have some status on CI as well, made an issue .
As other point out, you should be able to use GitLab CI instead of Travis, they configure very similarly. That said, I'd welcome them integrating fully with us as well.
As for other projects - the most important one for me was clubhouse.io (Gitlab Issues is great but just not as good as clubhouse.io)
Ah interesting! You can't do this now with GitLab, but we're working on supporting merge requests as special cases .
> As for other projects - the most important one for me was clubhouse.io (Gitlab Issues is great but just not as good as clubhouse.io)
Clubhouse sure looks nice! GitLab Issues is getting better every release and in 9.0 (March 22nd), we have some big changes for Issue Boards.
I've asked our PM on Issues (Victor) to check out Clubhouse and hopefully we can convince them to integrate with us in some way.
When I firsted started as a developer, I don't know how people do thing in real production. I don't know how real company build real software.
Nowsaday, with all open source thing from real company that acquire/shutdown I can finally learn a lots from them.
Recently Stajoy open source everything, now Gitter is next. I'm sure I will learn a lot by consume the real code that run on production.
Thank you Gitlab/Gitter.
The goal seems to be to have the code open sourced by this June, with all history included.
Stack details here: https://stackshare.io/gitter/gitter
By tapping into those conversations, they'll probably be better able to identify GitHub pain points and provide subtle hints and nudges, for Gitter users to consider GitLab.com
Looking forward to updates, thanks!
I'm currently in the processor of migrating an OSQA site to AskBot, which seems currently maintained.
Google cache: https://webcache.googleusercontent.com/search?q=cache:XWzfaA...