Hi @Tom,
Appreciate your interested and your thoughtful feedback these last few days. A few thoughts:
- Mattermost is a explicitly a self-hosted team communication solution providing an alternative to proprietary SaaS.
- What matters most for teams is not what matters most for a proprietary SaaS service, and accelerating the use of proprietary SaaS is not a priority of this project.
For example, the idea of requiring permission to change a channel header doesn't fit the criteria for being a bug.
In a team, when someone changes the header, they're probably trying to be helpful. Any change is recorded in the channel, so if it wasn't helpful, a polite conversation can occur to correct.
To translate this to a real world example, when you walk into a conference room there aren't permissions to use the whiteboard, there is a social norm in teams to use it appropriately.
You are more than welcome to open a feature idea (and perhaps an offer to contribute) if you feel this change is a priority.
We purposefully use the voting system, rather than GitHub issues, so:
- Community members who are less articulate (particularly those whose English is not as strong) can be influential
- There's more clarity on what the community wants, versus individuals.
Each system--feature idea forum (feature ideas), GitHub issues (bugs), forum (troubleshooting and discussion), pre-release (contributor discussion and testing of pre-released versions), Jira (approved work items)--serves a specific purpose, just as the product serves a specific purpose.