tickets #63622
closedEstablishing the strategy for establishing bridges between communication channels
100%
Description
This is the list of items which will have to be done post setup of the Matrix bridge. This is being coordinated by Stasiek Michalski <stasiek@michalski.cc>, however everybody is welcome to help out.
PLEASE NOTE: channel names on the Matrix side should not contain 'openSUSE', that's already a part of the channel name with the server url (eg. #chat:openSUSE.org and not #opensuse-chat:openSUSE.org)
Matrix.org -> openSUSE.org¶
All of the existing channels will be moved to openSUSE.org homeserver
Steps for completing the task:
- Set up tombstone events for the existing matrix.org rooms
Freenode.net -> openSUSE.org¶
All of the active Freenode channels will get bridged to the corresponding openSUSE.org homeserver rooms (plumbed rooms)
Steps for completing the task:
- Create or join the corresponding room for bridging on the openSUSE.org homeserver
- Check the internal Matrix room ID
- Set up via salt pillar profile:matrix:appservices:irc:channels filling in correct freenode channel and internal room id
- Continue with the common room settings
Discord -> openSUSE.org¶
All of the Discord channels are already bridged with the existing Matrix rooms, this will all have to be redone using the new bridge.
Steps for completing the task:
- Remove the current Matrix Webhooks in the bridged channel on Discord
- Create or join the corresponding room for bridging on the openSUSE.org homeserver
- Invite
@_discord_bot:opensuse.org
to the room - Give the bot moderator permissions
- Run
!discord bridge <gid> <cid>
(how to obtain gid/cid) - Approve from the Discord side
- Continue with the common room settings
Telegram -> openSUSE.org¶
Some of the Telegram rooms are already bridged with the existing Matrix rooms, this will all have to be redone using the new bridge.
Steps for completing the task:
- Invite
@openSUSEMatrixBot
to the Telegram room - Use
/id
command in the Telegram room - Create or join the corresponding room for bridging on the openSUSE.org homeserver
- Invite
@telegrambot:opensuse.org
to the Matrix room - Give the bot moderator permissions
- Use
!tg bridge <id>
command, replacing id with the output of the Telegram command in the Matrix room - Continue with the bot's instructions
- Continue with the common room settings
Gitter -> openSUSE.org¶
There are some openSUSE related Gitter channels
Steps for completing the task:
- Create or join the corresponding channel for bridging on the openSUSE.org homeserver
- Use the "Manage Integrations" menu on Riot to bridge the room with Gitter
- Continue with the common room settings
Further integrations¶
Depending on the wishes of the teams managing the channels, we will also be setting up secondary bots/integrations.
Common room settings¶
This is the list of default settings channels should follow on the matrix server
- Room Title:
openSUSE *alias*
in Title Case - Room Description:
+rooms:opensuse.org | Bridged with x, y and z | *the function of the channel*
translated to the language of the channel (please keep in mind the description is not a good place for announcements, use pins instead) - Room Icon: reach out to the Artwork Team on
#artwork:opensuse.org
;) - Enabled flairs: [+discord:opensuse.org, +freenode:opensuse.org, +telegram:opensuse.org, +members:opensuse.org]
- Publish to the public room directory
- URL Previews enabled by default for the participants of the room
- Access to the room for everyone, but guests (with the exception of support/info channels)
- Info channels have permissions required to send messages at moderator
- Anyone can read history
Updated by hellcp over 3 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 50
We have most of the bridges going
Updated by hellcp about 3 years ago
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
Ok, I'm closing this since we have solutions for methods, but no implementation yet, which will be done over the next few months