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.<p>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.
Every next move by Gitlab makes them grow in my eyes, personaly. Few weeks ago I started using it as my main "portfolio", it's not much but I really like their way of thinking, openness and providing services. Their whole eco-system is looking really interesting right now, and I hope they will continue to advance and grow.<p>Edits: typos, wrote from phone.
Up until this week I was in love with Gitlab. We've been using it at work for over a year as our main repo, code review tool and CI (tried self-hosted first, then moved to gitlab.com).<p>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).<p>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).<p>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.
@sytse - this is huge. You can move the YC internal slack to gitter as well ;)<p>But seriously - people are willing to throw money for an enterprise gitter - especially after <a href="https://medium.freecodecamp.com/so-yeah-we-tried-slack-and-we-deeply-regretted-it-391bcc714c81#.ki286cqbu" rel="nofollow">https://medium.freecodecamp.com/so-yeah-we-tried-slack-and-w...</a><p>Look at the number of people begging Discord to take money from them - <a href="https://feedback.discordapp.com/forums/326712-discord-dream-land/suggestions/12454674-discord-as-a-replacement-to-slack-for-developers" rel="nofollow">https://feedback.discordapp.com/forums/326712-discord-dream-...</a><p>gitter always had search working - discord just got it recently.
"Next piece of wow: we will be open sourcing all of the Gitter"<p>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.
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 of taking on Slack more directly?
Confirmed on Twitter: <a href="https://twitter.com/gitchat/status/842058103571001344" rel="nofollow">https://twitter.com/gitchat/status/842058103571001344</a><p>Link to the live post: <a href="http://blog.gitter.im/2017/03/15/gitter-gitlab-acquisition/" rel="nofollow">http://blog.gitter.im/2017/03/15/gitter-gitlab-acquisition/</a>
This is pretty weird to me:<p>> What about Mattermost, how is this different?<p>> 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.<p>> Mattermost is a powerful, integrated messaging product for team collaboration - we will continue to ship and recommend using Mattermost for internal team communication.<p>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.
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
This appears more like a acqui-hire. Also, since mattermost is bundled as part of GitLab, it makes me wonder why they didn't acquire mattermost instead.<p>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).<p>Third, people see GitLab as GitHub competitor. But really it competes with Atlassian.
I hope this spurns more OSS communities to move to gitter. As much as I enjoy slack, limits on features like search and invites creates a friction that I think a service like gitter can help solve.
I'm a member of a Gitter for a smart mirror project. It's been a fun way to connect with other fans of the project and the maintainers. Feels like a smart move.
This seems like a good match.<p>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.<p>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.<p>edit; typo
That is awesome news. I have been using Gitlab for the last year. I switched over my personal projects and 3 organizations I was advicing from GitHub.
They won me with their data centers in Asia and Europe.
GitHub is extremely slow in Asia and they do not want to change.
I love Gitlab but sadly, quite a lot of services that offer free accounts for open source projects (TravisCI comes to mind), generally don't integrate with Gitlab<p>It's one of the few reasons why I am still using Github :( .
I really like Gitlab and this acquiring.<p>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.<p>Nowsaday, with all open source thing from real company that acquire/shutdown I can finally learn a lots from them.<p>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.<p>Thank you Gitlab/Gitter.
Discussion at: <a href="https://gitter.im/gitterHQ/gitter" rel="nofollow">https://gitter.im/gitterHQ/gitter</a><p>The goal seems to be to have the code open sourced by this June, with all history included.<p>Stack details here: <a href="https://stackshare.io/gitter/gitter" rel="nofollow">https://stackshare.io/gitter/gitter</a>
What the heck is Gitter? A public chat service? Sounds like adding yet a new way for people to bug you about things that don't work, but without the controlled discussion of opening a proper Issue. As a developer or maintainer, what value does this bring to a project?
Think about your favorite github repo, or even just a very specific one, and there is always a few people talking about this repo: <a href="https://gitter.im/rails/rails" rel="nofollow">https://gitter.im/rails/rails</a>
Url changed from <a href="http://blog.gitter.im/p/7e1c7194-347e-47f1-84d1-8149de853e03/" rel="nofollow">http://blog.gitter.im/p/7e1c7194-347e-47f1-84d1-8149de853e03...</a>, which disappeared.
I hope the search in gitter-chanels gets better now, cause of open-sourcing it. There are good infos and tips hidden. Maybe tags or upvotes would solve this.
So somewhat eerily, my Gitter GitHub public repo authorization token shows that it was accessed within the past 2 days, despite my not having logged in to any Gitter pages in months.
<a href="http://imgur.com/a/aABi8" rel="nofollow">http://imgur.com/a/aABi8</a>
next, I hope to see some "content" offer attached to gitlab's ecosystem, for instance a strong collaboration with stackoverflow/OSQA
This leads to 404. Their official blog says nothing about it (<a href="http://blog.gitter.im/" rel="nofollow">http://blog.gitter.im/</a>) and Twitter also says nothing about it (<a href="https://twitter.com/gitchat" rel="nofollow">https://twitter.com/gitchat</a>).