570 karma · joined May 1, 2012
Did you want to turn off smiley-to-emoji conversion for your own view, or on how others view your messages, or as an admin feature for the server?
There's an upvote and discussion thread on this, would welcome your input: https://mattermost.uservoice.com/forums/306457-general/sugge...
1) For End Users and Developers, Golang can mean fewer bugs
Golang is a "type-safe" language, meaning that all the programming code is written to be explicit and consistent, versus "untyped" languages like PHP or JavaScript, where programming is more implicit with many different ways to say the same thing.
It's easier for software tools to automatically analyze type-safe languages and find bugs. And those languages are also easier to read and review--since there's only one way to express something--and that helps too.
2) For System Administrators, Golang means easier install and management
Golang is a "complied language", meaning that after the programming is done, a single file is produced. So a System Administrator just installs one file and Mattermost works. To upgrade, they just change that one file. Easy!
Languages like PHP and JavaScript are "interpreted languages", meaning that a System Administrator would need to download lots and lots of files, install one or more programs to interpret those files, and hope that nothing breaks. When it's time to upgrade, she's got to make sure all the files and interpreters on her server are exactly the right version. It can be a nightmare to maintain.
3) So what's the trade-off?
The trade-off with Golang is that it takes more work to learn than PHP and JavaScript. The programming language isn't as forgiving to new programmers. You need to say things exactly the right way or the program won't even start, whereas PHP and JavaScript if you say things "kind of right" and things will "kind of work".
Does this help?
Could you share an example of what you went wrong?
The Mattermost server has around 59% automated test coverage, our community does over 120 hours of manual testing prior to each monthly release, and we're constantly striving to improve.
Here's a recent review of Mattermost's quality levels, from someone who left Mattermost and then returned, concluding Mattermost was the leading solution: http://www.akitaonrails.com/2016/08/13/choosing-mattermost-o...
If your experience is different, we're highly interested in knowing how we can improve.
Yeah, we love using threads to keep discussion on track.
It took a long time to design. We weren't able to find anything like it, and had to design through a lot of corner cases.
We're still working on making it more discoverable. Once you use it, it's hard to go back, but it takes a while for people to discover the "Reply" button on messages.
Definitely hear your feedback on the custom tier, we'll try to figure something out this next week.
The iOS app is a feature rich experience similar to web and desktop apps, so when I travel and am on a slow connection it doesn't perform as well.
Here are our current mobile performance benchmarks so you can decide for yourself: https://docs.mattermost.com/deployment/push.html#mobile-perf...
There's work underway to get the mobile apps working better on slow connections.
Highly appreciate your feedback.
Our intention is that 99% of people use Mattermost Team Edition under MIT.
You're right about that trademark section under MIT, that is weird, we'll remove it in the next release.
For the 1% of people who want to modify the core /platform, we're just asking they share back to the community.
Here's a summary of our licensing and philosophy: https://www.mattermost.org/licensing/
Mattermost team here. Thanks for your feedback,
While pricing is set that way for a purpose, we are always looking for ways to improve and we're keenly interested in what everyone has to say.
Our focus for Enterprise has been large organizations with sophisticated needs and it's important for us to have conversations and demonstrations with the people doing the evaluation so they fully understand what we're offering.
That said, there are people who use our free Team Edition or have read through our docs that just want a "buy" button for E20.
I'll bring this up and see what we can do.
PS: Regarding the word "fix", my personal view is that it's okay for a commercial product, because people are buying it as a customer. Enterprise Edition is a commercial product.
That said, many open source communities are adopting a principle of "kindness" and having feedback phrased positively where possible. People work hard to make open source software and give it away, and if conversations started on a positive note... well, why not?
You can also talk to Mattermost team on #matterbridge on Freenode.
Anyone interested, you can find Mattermost install guides here: http://www.mattermost.org/installation/
Puppet, Docker, Cloud Foundry, Heroku, plus guides to install directly on Ubuntu, Debian and RHEL/CentOS/Oracle Linux, etc.
Forums available for any help getting started beyond docs: https://forum.mattermost.org/
So if part of your team wants to stay on IRC and part wants to use Mattermost with file sharing and messaging across PC and phone, and integrate with Mattermost apps (http://www.mattermost.org/community-applications/) all that is available.
Just to add, you can use IRC clients to connect to Mattermost https://twitter.com/mattermosthq/status/668898122630721538
Community has asked this for a while, we want to build an effective, well documented API to let the community create what they want: http://mattermost.uservoice.com/forums/306457-general/sugges...
We're working on shipping a high quality set of APIs. We're doing these in parts so we can design and document them well.
Mattermost v1.1 ships on October 16 and offers incoming webhooks as a start: http://www.mattermost.org/webhooks/
You'll find a link there to an open source sample app for customizing how you want webhook events from GitLab to appear.
Mattermost incoming webhook support ships with GitLab 8.1 on October 22.
For Mattermost v1.2 (November 16), we're working on outgoing webhooks, which could offer the ability to fire off console commands.
We had dozens of community members upvote a feature to add markdown and we added it because it made sense.
Now we really love it and can't go back: http://www.mattermost.org/open-source-slack-alternative-adop...
Headings have a lot of uses for emphasizing text, and there's fun uses too like creating different sized emoticons: http://www.mattermost.org/wp-content/uploads/2015/09/sheep.p...
##### :sheep:
#### :sheep:
### :sheep:
## :sheep:
# :sheep:
Mattermost team here. We've had requests for XMPP, and potentially it can be added in future. Feature idea can be tracked here (and more ideas welcome!): http://mattermost.uservoice.com/forums/306457-general/sugges...
That said, communication has changed significantly since the XMPP standard. For example, after we implemented markdown in Mattermost it's really hard to go back (http://www.mattermost.org/open-source-slack-alternative-adop...).
If you decide to try Mattermost, please let us know if we can help! Twitter at @mattermosthq or via community options at http://www.mattermost.org/
One note to add is that the standard version of Mattermost is Apache-AGPL similar to MongoDB. So any organization comfortable with MongoDB should be fine with Mattermost.
MongoDB and Mattermost have Apache for drivers, configuration and administration so you can use and deploy the binaries without restriction. If modifications are made to the core product, those are required to be shared with the open source community.
Thanks for the mention! Happy to answer any questions.
Here's links to community resources: http://www.mattermost.org/
The text of the screenshot was actually written in Slack, and the goal of the screenshot was to demonstrate the Slack Import feature to GitLab Mattermost.
On the GitLab Mattermost page (https://gitlab.com/gitlab-org/gitlab-mattermost) there was a subtitle describing this, but we could have made it more clear in the screenshot itself.
First step would perhaps be filing a feature request so the community can upvote: http://www.mattermost.org/feature-requests/
When we talked to potential users, XMPP didn't come up as a priority, and we haven't yet had a feature request filed for it.
Very happy to have it added so XMPP can be upvoted: http://mattermost.uservoice.com/
Please feel free to comment as well, as there's different variations of this feature (Mattermost to Mattermost team, or Mattermost to Slack team, etc.).
In terms of messaging functionality, there's nothing ground-breaking about the UI, our focus is on avoiding what happened to SpinPunch when we were previously locked in to a proprietary SaaS messaging service: http://www.mattermost.org/why-we-made-mattermost-an-open-sou...
That said, Mattermost was originally designed to be a games portal (not just a messaging app), and you'll probably see the UI bring that functionality back in the "AppCenter" feature being developed: https://docs.google.com/document/d/1s6vrticxgz9PsxePQ-dFrsKp...
We're working on getting our issue tracking system transparent so the community can see everything that's being worked on.