I don’t think we want to run something critical for chatting, but I do think we want the namespace.
- Give us access to jenkins.io namespace
- jenkins@matrix.org goes to some random “devops” channel and we can’t do a whole lot about it.
- can setup a space for all channels. Matrix has the concept of spaces, kinda like discord, where you can add all the channels for a community, and it’ll show up in the space. You can still join specific channels, but see everything
- Somewhere sane to put bots (jenkins-admin, discourse, etc)
We wouldn’t need to allow users to use the homeserver at all, just add it to the known addresses.
For example, the jenkins main room’s main address is #jenkinsci_jenkins:gitter.im but lots of people have @matrix.org accounts. Its also #jenkins:g4v.dev (okay its not, but it could be)
Implementation
- Use synapse. Its a really big python project that does way more than we need (
from me) - Use a hosting service such as Element plans and pricing and see if they have any sort of sponsorship package
- Use dendrite - Go version of the home server, probably pretty light weight, just needs a db
- Use conduit - super light weight written in rust. Not sure it supports spaces yet
Throwing it out there as I can’t/dont want to reach out for sponsorships these days.
On a side note. I’m up for upgrading jenkins-admin bot to speak matrix if we want to phase out the irc channels