matrix bridges for #tor-space:matrix.org and related
Please plumb the following matrix room(s) to its IRC counterpart(s) on oftc:
- all of
#tor-space:matrix.org, starting with: -
#tor-admin:matrix.org, plumbed toirc.oftc.net/#tor-admin
Additional notes, if any:
This is a WIP/draft issue: we're not quite ready to migrate yet, but we'd like to start testing with a few channels. #tor-admin is ready for testing, once that's done, we will proceed with the rest after a test period.
For now, here are the various rooms and their equivalent IRC channels:
| IRC | Matrix | Topic |
|---|---|---|
#tor |
#tor:matrix.org |
general support channel |
#tor-project |
#tor-project:matrix.org |
general Tor project channel |
#tor-internal |
N/A | channel for private discussions |
#cakeorpie |
N/A | private social, off-topic chatter for the above |
#tor-meeting |
#tor-meeting:matrix.org |
where some meetings are held |
#tor-meeting2 |
N/A | fallback for the above |
#tor-admin |
#tor-admin:matrix.org |
TPA team and support channel |
#tor-alerts |
#tor-alerts:matrix.org |
TPA monitoring |
#tor-anticensorship |
#tor-anticensorship:matrix.org |
anti-censorship team |
#tor-bots |
#tor-bots:matrix.org |
where a lot of bots live |
#tor-browser-dev |
#tor-browser-dev:matrix.org |
applications team |
#tor-dev |
#tor-dev:matrix.org |
network team discussions |
#tor-l10n |
#tor-l10n:matrix.org |
Tor localization channel |
#tor-network-health |
#tor-network-health:matrix.org |
N/A |
#tor-relays |
#tor-relays:matrix.org |
relay operators |
#tor-south |
#tor-south:matrix.org |
Comunidad Tor del Sur Global |
#tor-ux |
#tor-ux:matrix.org |
UX team |
#tor-vpn |
#tor-vpn:matrix.org |
N/A |
#tor-www |
#tor-www:matrix.org |
Tor websites development channel |
#tor-www-bots |
N/A | Tor websites bots |
| N/A | !MGbrtEhmyOXFBzRVRw:matrix.org |
Tor GSoC |
That is 21 entries, including 20 IRC channels and 15 Matrix rooms, if i count this right.
Most channels currently marked "N/A" should probably not be bridge in the short term, in particular the two private channels, because a bridge wouldn't work anyways without the secret key. But we should probably bridge the current "N/A" ones as well. The Tor GSoc channel should probably be aliased to #tor-gsoc:matrix.org and bridged over to IRC, but it doesn't actually exist on IRC, so I'm not sure what to do with it.
I'm waiting for feedback from the others to see which channel we should start with, as I don't think we should do all of those at once.
Also note that we're considering running our own mjolnir (draupnir, in fact), so deploying @mjolnir (below) possibly won't be necessary... We would love to have the bot join too, although I think i can do that myself as i'm in that room (#mjolnir-management:matrix.debian.social?)!
Note that we're tracking this work on our side in https://gitlab.torproject.org/tpo/tpa/team/-/issues/42053
Check-list for Debian Social Team
-
Create the Matrix room(s)rooms already exist -
disconnect the old bridge (send !unlink !OPAQUE:matrix.org irc.oftc.net #tor-exampleto@oftc-irc:matrix.org, for example#tor-adminwas unlinked with!unlink !SocDtFjxNUUvkWBTIu:matrix.org irc.oftc.net #tor-admin) -
Link the room to IRC within the matrix-appservice-irc config bundle -
Deploy the changes ( ssh config.debian.social 'git pull && bw apply matrix_ds') -
Invite social team and@mjolnir:matrix.debian.social as admins -
Invite requester as admin if applicable -
Add room to #debian:matrix.debian.social space -
make sure matrix_dsuser joins on IRC