Re: [opensuse-web] openSUSE PaaS meeting minutes 2018-01-17 Kick-Off

Hello Adam, there many good reasons why we shouldn't use Slack and I agree with what you said. But there are a couple of reasons why we agreed to use it: - Asynchronous communication. People involved do not share the same schedule. That means, whatever is written in irc gets lost unless you are online at the time of writing. - People from outside the company should be able to join (with whatever email). There might be more (mobile clients, etc), but the 2 above are the most important. Slack was not supposed to be our community chat, but rather an easy way to get us moving. Feel free to suggest alternatives but let's not get lost in the chat tooling before we even have something to talk about. Kind Regards, Dimitris P.S. I would love to see a public rocketchat instance hosted on our CloudFoundry (as soon as we have one running). On 02/01/2018 06:45 PM, Adam Spiers wrote:

Hi Dimitris, Dimitris Karakasilis wrote: >> Also, >> >> you should have got an invitation for the slack channel.

...

Apologies in advance for wading in with some negative comments, but hopefully they can be taken as constructive rather than flames ;-) > I'm not sure it's a great idea to introduce Slack, at least not > without first discussing with the wider openSUSE community: 1. It > fragments the existing IRC community. > > 2. It introduces a dependency onto centralized, proprietary > technology. This does somewhat conflict with the freedom-oriented > goals of the Project. > >> If you didn't, you can still join using your `suse.com` email >> address here: > > [snipped] > > This is a public openSUSE list, so not everyone here is a SUSE > employee or has a @suse.com address. As SUSE employees we need to be > careful to avoid creating a two-tier culture, since openSUSE belongs > to everyone ;-) Hope this helps, Adam