It turned out there already was an openSUSE Slack so we moved the chat there. Join the openSUSE workspace here: https://join.slack.com/t/opensuse/shared_invite/ enQtMzA2MTA1MzAxNTY4LTc4OGY4YzI2YzIyYzRmOTJhMmRmYzdlNGEwMWJhOTYwM2EyNDEwMzVhNGEyOGQ2OTVmYWUwMDM3NzY2MjRmYjU Then join the #paas channel for the discussions around setting up a PaaS for openSUSE. On Mittwoch, 17. Januar 2018 16:43:46 CET Dimitris Karakasilis wrote:

Also,

you should have got an invitation for the slack channel. If you didn't, you can still join using your `suse.com` email address here:

https://join.slack.com/t/opensuse-paas/signup?x=x-299602494320-300280387394

On 01/17/2018 05:20 PM, tbro@opensuse.org wrote:

...

For the record...

openSUSE Paas Kick-Off

0.1 Quick introduction round as not everybody knows everyone 0.2 What do we need to do? (hardware, software, infrastructure to set up)

0.2.1 Getting hardware

0.2.1.1 Admin node (minimum: 4 cores, 8GB RAM) 0.2.1.2 1 Master (8GB MEM, 4+ CPUs) 0.2.1.3 2 Minions (16GB MEM, ???, decent HD space: minimum

60GB per node)

0.2.2 Figure out network topology/requirements

0.2.2.1 Everyone who wants to involve himself technically

should get an openSUSE VPN Account -> admin@opensuse.org

0.2.3 Figure out storage requirements 0.2.4 Deploy CaP https://github.com/suse/scf

(https://github.com/SUSE/scf/wiki/How-to-Install-SCF)

0.2.4.1 LDAP/Account 0.2.4.2 Storage (Ceph?) (need a valid Kubernetes storage class

https://kubernetes.io/docs/concepts/storage/storage-classes/ )

0.2.4.3 Kubernetes / CaaSP 0.2.4.4 CloudFoundry / SCF

0.2.5 Take two applications and deploy them

0.2.5.1 OSEM https://github.com/openSUSE/osem

0.2.5.1.1 current resources: http://paste.opensuse.org/view/raw/63724338

0.2.5.2 software https://github.com/openSUSE/software-o-o

0.2.5.1.1 current resources: http://paste.opensuse.org/view/raw/80840487

0.2.5.2 everything behind static.opensuse.org

https://github.com/openSUSE/landing-page 0.3 How are we going to move forward? (tools to use, meetings to hold, people to invite etc.)

0.3.1 Invite someone from the CaaSP team (Richard Brown?) 0.3.2 Have a communication channel

0.3.2.1 Slack channel (Dimitris) 0.3.2.2 Mailing list: opensuse-web+subscribe@opensuse.org

0.3.3 Have a tool to spread tasks

0.3.3.1 Trello https://trello.com/b/5rcSlDX1/geekops

cheers, Thorsten

-- Cornelius Schumacher -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org

Hey, On 01.02.2018 17:45, Adam Spiers wrote:

I'm not sure it's a great idea to introduce Slack, at least not without first discussing with the wider openSUSE community:

We are only 'introducing' slack for our own little project that we nurture currently. We are very well aware of the problems of slack or any other centralized, proprietary service. However we choose to ignore this as slack fits us a group best currently. Like many other groups in openSUSE use other things that fit them best...

...

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.

In the meantime we switched to some other slack that, as far as I understand, does not have this limitation. Thank you anyway for expressing your concerns, Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org

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