3 ms·

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. This i

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. 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.

it33 10y ago
Hi @simplehuman, Mattermost team here, thanks for the mention. 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-source-slack-alternative/ 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.html 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 https://github.com/mattermost/platform/pull/5718 Previous related example: https://github.com/mattermost/platform/pull/2718 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/ 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/ https://pre-release.mattermost.com/ Third, yes, agree, GitLab is certainly competing with Atlassian, and winning a lot.
deleted 10y ago
[deleted]

it33 10y ago

Hi @simplehuman, Mattermost team here, thanks for the mention. 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-source-slack-alternative/ 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.html 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 https://github.com/mattermost/platform/pull/5718 Previous related example: https://github.com/mattermost/platform/pull/2718 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/ 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/ https://pre-release.mattermost.com/ Third, yes, agree, GitLab is certainly competing with Atlassian, and winning a lot.

deleted 10y ago

[deleted]