570 karma · joined May 1, 2012
Just curious, have you enabled the GitLab-Mattermost plugin? https://github.com/mattermost/mattermost-plugin-gitlab#confi...
If it wasn't easy to find, that's on us, and we need to do a better job in making things more discoverable.
Now asking folks to add `Enhancement:` prefix on tickets, and we can label after
Hi @eps, I've opened a ticket on this: https://github.com/mattermost/focalboard/issues/99
Would you be open to giving a "Thumbs Up" and/or a comment sharing more about the benefits?
Community feedback is super important, and we would love to hear more from you and others
Huge thanks to everyone who's sharing feedback and comments. It is super exciting to be trending on HackerNews!
We've just put up a new Wiki page for people to share feature ideas, to join our Discourse forum, and to report bugs: https://github.com/mattermost/focalboard/wiki/Share-your-fee...!
Thank y'all so much for being interested in our project and our space!
We've been working super hard to make something people love, and we'll continue to do so with your input and ideas!
Thanks for your feedback!
We'd love to hear more. We just setup this page with links on how to get more involved: https://github.com/mattermost/focalboard/wiki/Share-your-fee...!
We weren't aware of Open Project previously, and we're glad to hear about it.
I think you're right, Focalboard is a lot earlier than Open Project, and it doesn't have as many features.
Focalboard was starting during the Mattermost 2020 Hacktoberfest last year: https://mattermost.com/blog/hacktoberfest-2020-recap/
It's in the early stages of development, only v0.6 right now: https://github.com/mattermost/focalboard/blob/main/CHANGELOG...
That said, we're working on it constantly and excited about its future.
Of the features Open Project has now, are there one or two top priorities you'd suggest we consider adding to Focalboard?
We'd love to hear any feedback, feature suggestions or bug reports: https://github.com/mattermost/focalboard/wiki/Share-your-fee...!
We're working super hard to build something that benefits our community.
While there's not formal support for Raspberry Pi right now, we'd welcome a the feature idea, here's more on how to share feedback: https://github.com/mattermost/focalboard/wiki/Share-your-fee...!
Added an enhancement ticket for this: https://github.com/mattermost/focalboard/issues/95
Open to other feedback as well! https://github.com/mattermost/focalboard/wiki/Share-your-fee...!
Hi @kogepathic, sorry about that, adding your report as a ticket here: https://github.com/mattermost/focalboard/issues/94
You can try the "Focalboard Personal Desktop" to run locally where your performance won't be affected by other users.
We made it available in Windows Store and Apple AppStore to make it easy to try out.
This is just a v0.6 right now, and we would love bug reports and enhancement ideas.
It's the early days of the project and we are excited to hear input: https://github.com/mattermost/focalboard/issues
Hi @riho, thanks for your feedback. One key piece of feedback we've heard is that other SaaS-based project management tools can run slow.
Because of this, one concept we're testing out is "Focalboard Personal Desktop" where you can run the software locally.
You can download the v0.6 version from the Windows Store or Apple AppStore to try it out. We would love your feedback.
Also, if you're interested in influencing the project, please consider submitting a ticket with type `enhancement` with what you'd like to see: https://github.com/mattermost/focalboard/issues
This is when we were largely just an open source project and before raising $70M in venture capital, which has been accelerating development: https://mattermost.com/blog/category/releases/
1) Enforcing password requirements for end users was put in free tier last year - Here's why, with a link on how to use it: https://github.com/mattermost/mattermost-server/issues/5935#...
2) Non-admins are still able to archive channels they belong to but did not create - Here's why: https://github.com/mattermost/mattermost-server/issues/6320#...
3) I need to work on speaking more concisely, here is another version of #2 from an HN user who puts things more simply: https://news.ycombinator.com/item?id=21824219
Does this help?
On hiring, yes, we're hiring too, that's perhaps the most committed route to take: https://mattermost.com/careers/
Would love to squash the bug for you, open to filing an issue?> https://github.com/mattermost/mattermost-server/issues/new
We used to send bug coins just for release candidates, but if you find a bug in production you get one too now: https://www.youtube.com/watch?v=7D6FJsdE_aY
Mattermost is already certified on Aurora, we work with S3, it's available in AWS Marketplace--if there's a dev team at Amazon interested in an open source alternative to Slack that runs natively on AWS infra--potentially connects with Chime for voice/video/meetings/screenshare it's potentially a healthy thing for everyone.
Fantastic! Thanks for sharing back--comments like this are super motivating for everyone working on the project,
Thanks for the feedback, replies on both issues posted:
https://github.com/mattermost/mattermost-server/issues/6320
https://github.com/mattermost/mattermost-server/issues/5935
Please let us know what y'all think?
The password policy was added to Team Edition back in June, 2018.
>Mattermost isn’t any kind of a competitor to free-tier Slack
Mattermost isn't intended to compete with Slack's free tier.
The open source version of Mattermost is focused on software builders and operators who want a flexible, open, collaboration platform that works with their tools and workflows. Here's more on Mattermost Chatops as an example: https://mattermost.com/blog/introducing-mattermost-chatops/
Very often we're deployed in high security environments and private clouds where internet-based services can't easily go.
Opened a ticket here: https://github.com/mattermost/mattermost-server/issues/13422
Thanks for highlighting this. It's a ticket from two years ago and this thread is a good opportunity to share more of the context and intention of how we think about Team Edition vs Enterprise Edition.
I've shared a reply on the ticket here: https://github.com/mattermost/mattermost-server/issues/6320#...
Also, I don't know if the ticket title is highly accurate--a non-admin can't delete any channel:
1) There is no "Delete Channel" in the UI only "Archive Channel"
2) A non-admin cannot archive any channel, only channels of which they are a member.
3) A non-admin archiving a channel they created is not really an issue, so this ticket is really about a "Non-admin can archive a channel which they are a member of but didn't create" which we've seen can be more helpful than harmful--when someone leaves a team and their out-of-date channels remains anyone can go and archive them without having to find an admin and make a request.
The current wording sounds like non-admins can delete private channels, channels on different teams, channels they're not part of, etc. and in my mind it's not the case. But perhaps other people have a different read?
Awesome work on raspchat! And thanks for the kind words.
Often we see users and customers have both Microsoft Teams for Office365 users and Mattermost as the "developer's choice" given the open source code base and flexibility in high security environments.
Per the article, the market is very large, and there's many different user segments to serve. Therefore there should be multiple winners here, in my mind. I think this category is only just starting.
As an example, when we were starting the Mattermost open source project we were considering a few options for different reasons:
1) Erlang - Real time properties made it nice for a high scale collaboration platform. The trade-off was that it's a really specialized language and there aren't that many people excited to learn Erlang.
2) C/C++ - Really powerful language and can compile to binary format, making install and upgrade easier for admins who don't want to be managing interpreted languages. Trade-off was it was an older language and there's fewer people excited about writing for it, and there can be a fair bit of nuance.
3) Python - Really popular, easy-to-read. Trade-off is things could get tricky as performance and scale needs increase. Also, doesn't support binary format, so more complex install and maintenance options would need to be used.
In the end we used Golang because it had many of the positive properties of Erlang, Python and C/C++ (compiles to binary, easy-to-read with gofmt, real-time support, etc.) and the trade-offs were fewer.