Site-Chat: Add features that enable mattermost to be used by webmasters/developers to power live chat conversations in floating windows on their web sites.
This would significantly increase proliferation and adoption of Mattermost.
Ask any adopters to link back to Mattermost via a small logo/link.
Features needed would be:
1) Automate creation of a new user in Mattermost via APIs (or support SSO, as the users would already be authenticated on the 3rd party site)
2) Create a renderer to bring up the Private Message channel in Mattermost between the 2 or more users that the 3rd party site chooses, probably triggered by a user or site action e.g. a JS function on the web page of each user to join a chat given a unique session code/name. The chat should be displayed on web page in an iframe only when the chat creation is triggered.
3) Since you'd use the default Private Message channel it would be only the two or more users who communicate
4) Any chat user should be able to close his chat window and re-open it, as long as the chat session is still open.
5) Should be able to CLOSE the chat session at which point the chat is terminated, cannot be re-used, however its contents can still be viewed
6) Chat should be archived and be retrievable by the system to display on a web page to a user and to send by email to the users.
You could change the email notification logic to send a link back to the archive after the conversation.

This feature is essentially a "force mute" in a meeting room, when you want to enable some people to listen in, but not to speak.

- Add an option to restrict the ability to post to a channel or private group (requires channel header menu redesign--the menu is over the UX guideline of 5-7 options per menu)
- Add the ability to define users who have the ability to post, which would by default include Team Admins. We don't currently have UX for a channel owner or channel creator, but in future Enterprise releases this may be added
- Include UX so that new users understand that they can read but cannot post. This is important in Town Square since it's the largest channel and most likely to be restricted, we need to avoid users joining being completely confused on how to post messages.

This is a complex feature in terms of UX, there's a lot of risk of user confusion, and therefore not a fit for Team Edition, and it could be added to enterprise, academic and non-profit offerings for large orgs.

It would be really useful if when a message contained text such as "blah blah blah bug 23 blah blah" that the text 'bug 23' was changed into a link to bug 23 in our issue tracker.

This could be handled more generally as a regex replacement that is applied to the message, with the system administrator being able to add multiple such regular expressions. This would allow all kinds of links, e.g. [[wp:Foo]] to link to the Wikipedia article 'Foo'.

The replacement could be applied at the point of save or the point of rendering, but I would recommend point-of-rendering so that (a) these can be retro-actively applied; and (b) that users are able to edit their posts in the form they were originally posted. Oh, and (c) if you find you've ballsed-up your regex for certain edge-cases you don't end up with mangled posts.

TortoiseSVN has a good implementation[1]. So I would suggest a variant on that.

For each replacement, there would be three fields (plus, maybe, some administrative fields e.g. to give the replacement a name):

1) A pattern to match the text that will trigger the linking ability. E.g. a naive implementation might consist of "[Bb]ug\s+\d+" which matches "Bug 5", "bug 1234", etc.
2) A pattern that searches within the previous match to extract link elements. E.g. "(\d+)" would extract the digits "23" from the matched text "bug 23". You could implement it to allow for multiple matches, but in practice restricting to a single field would probably be enough.
3) A URL that is used to create the link. In the URL $1 would be replaced by the matched string ($2, $3, etc. if you allow for multiple matches in step 2). E.g. "http://example.com/bugtracker/$1".

Using the above examples, the string "blah blah bug 23 blah blah" would be matched as follows:
* The first regex matches on "bug 23".
* The second regex matches on "23" within this string.
* The URL is therefore http://example.com/bugtracker/23
* The message output is therefore <a href="http://example.com/bugtracker/23&quot; target="_blank">bug 23</a>

The TortoiseSVN code is clever enough to match multiple bug numbers if you set up an appropriate regex. e.g. it could match "bugs 23, 25 and 27" and turn that into three separate links (in this case the word 'bugs' the comma and the 'and' would not be part of the links).

Note that the above implementation is just a suggestion, based on a very neat and flexible solution that I have used and which works well, but I'm sure there are many other implementation approaches that could be taken.

- HappyDog

[1] https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html#tsvn-dug-bugtracker-link-regex