Earlier quoted context omitted.
This just makes me hope you guys buy more things.
Ha! Any suggestions? ;)
https://typora.io/ (a WYSIWYG Markdown editor)
GitLab acquires Gitter, will open-source the code
111–120 of 333 posts
Re: GitLab acquires Gitter, will open-source the code
#112Somewhat 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…
I'm also turned off by remote companies that do the same. I work remote and moved to a very low-cost area. That doesn't mean I want a massive pay cut.
Re: GitLab acquires Gitter, will open-source the code
#113@sytse - this is huge. You can move the YC internal slack to gitter as well ;) 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…
> people are willing to throw money for an enterprise gitter
Isn't that just Slack?
Re: GitLab acquires Gitter, will open-source the code
#114I 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 It's one of the few reasons why I am still using Github :( .
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
Re: GitLab acquires Gitter, will open-source the code
#115Earlier quoted context omitted.
"Gitlab has some growing left to do, especially on the SaaS part." 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.
GitHub offers on-prem as well. Of course it's not open source and not potentially free like GitLab https://enterprise.github.com/features
$250/user/year, blocks of 10, min 10
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.
Re: GitLab acquires Gitter, will open-source the code
#116This 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 Atlassi…
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-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.
Re: GitLab acquires Gitter, will open-source the code
#117Earlier quoted context omitted.
"Gitlab has some growing left to do, especially on the SaaS part." 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.
Why? Github enterprise offers exactly that. An "On premises" Github.
Gitlab Enterprise pricing starts at $39/user whereas Github Enterprise pricing starts at $250/user so from that perspective Gitlab kicks ass.
Re: GitLab acquires Gitter, will open-source the code
#118Discussion at: https://gitter.im/gitterHQ/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
Re: GitLab acquires Gitter, will open-source the code
#119When 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