Consider using Slack?

[bernhold]

We needed to create a new Slack space for the BSSwF and I suggested naming it BSSw instead of being specific to the fellowship. This gives us options to consider using the space for either or both of:

1. An alternative to or supplement to the EB mailing list and GH issues -- a private channel for "internal" discussions
2. Creating space(s) for community discussion of BSSw.io, resources, etc. -- whatever we might want -- public or private, as appropriate

This is not something we have to decide now. The workspace is there (technically it is bssw-workspace.slack.com) and we'll be using it for fellowship stuff regardless.

[rinkug]

Do we need to pay $ for this?

[gonsie]

There is a no cost tier. Paying allows for an unlimited message history.

[rinkug]

A slack space has been created for the BSSw Fellows. Lets discuss this after Dec 2023 if this needs to be renamed to BSSw.io

[majidaldo]

completely disagree! https://usrse.slack.com/archives/C8ZB01CGH/p1697142504834389

Slack is the wrong medium for group communication.
Please allow me to demonstrate.
Slack is best for near-realtime communication. It encourages "walkie talkie" style communication.
This does not fit with the participation patterns of this group. There isn't much structure to the communication. I have to process a  "catch up", a wall of text, each time I log in. The longer that I'm away the harder this catch up is.
Alternatives: Anything that emphasizes writing paragraphs (...documents by extension) instead of messages. For example, a simple email list is better (but perhaps more modernized as in a google group). (edited) 

literally, since this is on github, github discussions is much better! "Issues" can just be specific to the website.

[rinkug]

Do we want to discuss this?

[markcmiller86]

We needed to create a new Slack space for the BSSwF and I suggested naming it BSSw instead of being specific to the fellowship.

Generalizing the name and purpose probably makes sense. That said, what is this giving us we don't already have via email?

This gives us options to consider using the space for either or both of:

1. An alternative to or supplement to the EB mailing list and GH issues -- a private channel for "internal" discussions

I think this (private) purpose is already served by email. Unpaid slack tier (which won't keep all messages in perpetuity) is no different from email IMHO and I find slack notifications a pain. It often notifies me (and I've found no way to turn it off) even for things that don't include me.

2. Creating space(s) for community discussion of BSSw.io, resources, etc. -- whatever we might want -- public or private, as appropriate

Well, interacting with the rest of the world is a different purpose. I suspect email is likely unfavorable for that. At least, I don't think most of the younger gen uses email much, do they. That said, why not GitHub discussions then.

This is not something we have to decide now. The workspace is there (technically it is bssw-workspace.slack.com) and we'll be using it for fellowship stuff regardless.

I am opposed to slack. Its harder to edit there (I write in markdown natively now), its another app I need to run, its constantly changing their interface, permissions, notifications, etc. And, I think it offers no advantages over GitHub discussions. I vote for

• A private repo for EB discussions that need to be kept internal
• The bssw.io public repo's discussions (or issues) for public discourse

We should advertise the latter on bssw.io site so people know where to go to jump in bssw.io discussions.