103
edits
(→3.Communication mediums: fix bulleted list nesting) |
|||
| Line 144: | Line 144: | ||
== 3.Communication mediums == | == 3.Communication mediums == | ||
* discourse forum? (judy). Discourse is completely different than discord. It's something you host yourself, and is a forum | * discourse forum? (judy). Discourse is completely different than discord. It's something you host yourself, and is a forum | ||
** Michael: a forum is too similar to email list, so we should choose one or the other. It's not a good idea to have two mediums that do the same thing. General saying for hackerspace, you want a wiki, a listserv, and an IRC. A Discoure forum would fall in the middle as a discussion medium. | |||
** Judy: Discourse is open source forum software that I like a lot, but I won't set one up if everyone is like "nooooo Judy no one wants to sign up for a new account, don't do it" | |||
** Michael: there is a possibilty MM could be single sign-on | |||
** Jake: we have very little buy-in on the email list and the Discord, but we have more on the Discord and I'd like to see that grow. If we were an open source software project group and everyone was at a high level of technical willingness and ability, then moving to Discourse woul make sense, but it's just practical that we have a wide spread of willingness and expeirence, and Discord is a sweet spot of "easy to use" | |||
** Michael: forum is "medium" while chat is "fast" | |||
** Jake: we have a forum in Discord! | |||
** Michael: I'm not in the Discord lol | |||
** Martin: do we know MM has a forum that we could use? | |||
** Michael: i think a better way is use MM as single sign on for Discourse login | |||
** Michael: Judy I think you should do it. Just let us know from technial aspect what kind of stuff do we need. Servers, domain names, any of that. | |||
** Peter: if we do this, can we have an overarching guide to communication mechanisms of Sudo Room? We have sooooo many. I'm of two minds on this. On one hand, it's good to reach people On the other hand, I can't track everything! Judy: me too | |||
** Michael: I have a write-up on community communciation methods that I can fix up and send to the mailing list. | |||
** Judy: yes Michael do that. | |||
** Peter: what problem does this solve? | |||
** Judy: I worry that Discord the company will delete their free tier, like Slack did. I would want to stop using Discord entirely and use Discourse instead, beause Discourse includes realtime chat!!!!!!! | |||
** Elaine: it's already happening! I can't change my name on different servers anymore, that's now a paid feature!!!! | |||
** Mick: Tamarack, for example, has multiple Signal threads. One is just for announcements that only admins can post to. The other is backroom organizing chat where most of the activity happens. There are ways you can organize community communications. | |||
** Peter: it's consistent with Sudo Room's mission that we need to be reclaiming the internet. I'm thinking for Michael and Judy there's an experimental group and part of it is promoting it where whatever is happening there is so cool that everyone wants to join it. | |||
** Michael: we should have ONE of each of these categories | |||
*** Slow: Document store: wiki (which we have) | |||
*** Medium: Forum but only one forum (and if we had Discourse, then we would NOT have email list, in Michael's estimation) | |||
*** Fast: Realtime communication. This one actually can be fragmented like on Signal, Discord, whatever | |||
* Creating a matrix space and bridge it with our discord (Michael) | * Creating a matrix space and bridge it with our discord (Michael) | ||
** Matrix is open source and federated | |||
** I tested the bridging using the service below, seem to work well | |||
** https://t2bot.io | |||
** https://github.com/matrix-org/matrix-appservice-discord | |||
== 4.Recurring member meeting in the future? == | == 4.Recurring member meeting in the future? == | ||