| But… stirring the pot can be a good thing, else the food sticks at the bottom of the pot and burns…
Mattermost is at its simplest, a team discussion and collaboration environment. There are the features of Mattermost:
Mattermost provides: * group chat * direct messaging * private chat rooms * messages, comments and description fields * a wide range of font formatting, headings, tables, and image embedding options * full markdown support * hashtags * Auto-highlight messages you wrote – to easily see what you said * file uploads - Share files and images internally and externally * archiving and search (including search by hashtag) * search public and private channels for historical messages and comments * view recent mentions of your name, username, nickname * support for multilingual teams * comment threads for easy-to-follow conversations. * personalize notifications for unread messages and mentions by source * Access anywhere: clients available for computers and mobile devices - attach sound, video and image files from mobile device * email interaction (through Mattermail) * IRC bridge (does anyone still use IRC? I haven’t in ages…) and also, in our particular case: * Eclipse project infrastructure for Mattermost (RSS, Git, Gerrit, Bugzilla, Eclipse Forums, Twitter, Mailing Lists, Jenkins/Hudson)
A lot of this can be done by email, but not everything.
I personally think it would be worth it to get off mail for this type of collaboration.
/Charles
I don't mean to stir the pot, but how is the Mattermost channel supposed to be different from this mailing list, other than where it is hosted? If both this list and the channel are open to the general public, and both are intended to discuss developer related issues, then which issues are supposed to be meant for the list and which for the channel?
It may be worth having something more independent from the rest of the infrastructure, but it seems like yet another means of communication to keep track of.
-- Ernesto
Perhaps Eclipse is paying for colo in some server farm run by Google? Looks like a complex setup anyways, but probably reasonably independent of the rest of the Eclipse infrastructure. Even so, keeping communications out of the email inbox and the mailman archive interface is a good thing.
On Mar 22, 2017, 13:10 -0400, Peter Cigéhn < peter.cigehn@xxxxxxxxx>, wrote:
Hi,
This service, and any data you submit to it, is maintained on a best-effort basis by Eclipse committers, using hardware sponsored by the Eclipse Foundation:
- The Eclipse Webmaster does not operate this service, it is a best effort by committers
- The data is not managed or maintained by the Eclipse Foundation
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
--
_______________________________________________ papyrus-rt-dev mailing list papyrus-rt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
