search

RITlug / infrastructure

This repository hosts all RITlug-related server configuration management.
Mozilla Public License 2.0
0 stars 0 forks source link

Bridge #sysadmin and #projects to Freenode #15

Closed ct-martin closed 5 years ago

ct-martin commented 5 years ago

So people not on Slack can participate

jwflory commented 5 years ago

#sysadmin on Slack is already bridged to #rit-lug-sysadmin on Freenode.

Tjzabel commented 5 years ago

@jwflory what steps can we take to bridge #projects to freenode? I'm assuming this is a matterbridge issue?

Tjzabel commented 5 years ago

Looking here I see the matterbridge configurations.

It says the #sysadmin channel's slack bot name should be mb-ritlug-sysadm. Am I reading this wrong? I ask because there is no user by that name, but rather by the slack-ritlug user. Has the ansible playbook for matterbridge not been updated/ran properly to reflect this name?

jwflory commented 5 years ago

@jwflory what steps can we take to bridge #projects to freenode? I'm assuming this is a matterbridge issue?

This can be a new issue filed on FOSSRIT/infrastructure. I can grab it later this week.

It says the #sysadmin channel's slack bot name should be mb-ritlug-sysadm. Am I reading this wrong? I ask because there is no user by that name, but rather by the slack-ritlug user. Has the ansible playbook for matterbridge not been updated/ran properly to reflect this name?

This is true for all the other bots as well. I can't remember if bot_name is different from the bot's nick. It may not be necessary but need to check upstream docs for clarification. I wasn't looking closely enough. I can't remember why I made a bot_name field. :woman_shrugging: It can probably be omitted without issue.

Tjzabel commented 5 years ago

@jwflory I added this as an issue there :+1:

ct-martin commented 5 years ago

For reference: https://github.com/FOSSRIT/infrastructure/issues/41

Tjzabel commented 5 years ago

This was completed.