So, I’m told that the new “Spaces” feature for Matrix/Element will be launching soon, and since so will Fedora’s Matrix-based chat server, we’ll be able to set that up. There’s supposed to be a blog post with details coming soon, but as I understand it this will allow us to present our communication channels to users in a hierarchy. So… how do we want to set this up? I’m thinking something like this:
- Help and Troubleshooting
- #fedora bridge (bridged to #fedora on Freenode)
- Fedora Devel [bridged to #fedora-devel?]
- Join Fedora [bridged to #fedora-join?]
- Social [also bridged to #fedora-social?]
Project Teams (each optionally bridged to a corresponding freenode channel)
- [etc – above example names just picked at random]
Meeting Channels (bridged to Freenode)
Does this make sense? Is there a better way to do it?
I’m a little bit concerned about just bridging Fedora Devel, Fedora Join, Fedora Social. There might be some… culture clash with the existing way of doing things in the channel, and maybe it’s better to have separate explicitly-bridged ones? Like, for example, the topic on #fedora-join is “Please register with Freenode to join the channel”, and the one on Fedora Social is… something about bacon? I’m wondering if it’d be better to start new channels here and then have a separate “Freenode Bridge” category?
Also, I’m wondering if we should break down the user converation thing into topics, and if so, how to best split that (edition? use case?).
And finally, there are a bunch of langage and locale freenode channels. Should we replicate those here too?