2 ms·
>>"Self-hosted Gitlab+Mattermost has been a very good bet for us so far." Any reason to use Mattermost now given that GitLab acquired Gitter (chat) [1]? [1] h
by tiffanyh 9y ago
>>"Self-hosted Gitlab+Mattermost has been a very good bet for us so far."
Any reason to use Mattermost now given that GitLab acquired Gitter (chat) [1]?
[1] https://venturebeat.com/2017/03/15/gitlab-acquires-software-chat-startup-gitter-will-open-source-the-code/ https://venturebeat.com/2017/03/15/gitlab-acquires-software-...
- andrewstuart2 9y agoWell, for one, it's still supported and actively included as part of this GitLab release [1]. I'm not sure their Gitter acquisition is intended to replace Mattermost. In fact, I wouldn't be surprised if it was integrated as an open, zero-overhead chat solution for a gitlab project, and then have it also presented in the mattermost client as a separate room for each project. That would be a really nice integration so that as a Dev, I don't need another chat client or browser window running, but I'm also not requiring my users to install my chat client or sign in separately in order to communicate. That said, I have no idea if their plans are similar to this or not. [1] https://about.gitlab.com/2017/05/22/gitlab-9-2-released/#omnibus-improvements https://about.gitlab.com/2017/05/22/gitlab-9-2-released/#omn...
- connorshea 9y agoWe describe our plans for Gitter / Mattermost in this blog post: https://about.gitlab.com/2017/03/15/gitter-acquisition/ https://about.gitlab.com/2017/03/15/gitter-acquisition/ We intend to keep both around as they serve different purposes :)