action #52532
Updated by okurz almost 5 years ago
## Motivation
Too many IRC+Rocket.Chat channels!!!1
## Situation
We have [#opensuse-factory](irc://chat.freenode.net/opensuse-factory]) as the official "openQA chat" channel, then [#testing (IRC)](irc://irc.suse.de/testing), [#qa-tools (IRC)](irc://irc.suse.de/qa-tools), [#openqa-dev (RC)](https://chat.suse.de/group/openqa-dev), <del>[#openqa (RC)](https://chat.suse.de/group/openqa)</del>, [#testing (RC)](https://chat.suse.de/channel/testing) as well as fallback channels such as [#suse](irc://irc.suse.de/suse), [#suse (RC)](https://chat.suse.de/channel/suse)
The topic to reduce some of the channels had been already discussed e.g. within [#openqa-dev (RC)](https://chat.suse.de/group/openqa-dev)
## Acceptance criteria
* **AC1:** bot is removed from #qa-tools
* **AC2:** team sees no necessity to stay in #qa-tools
* **AC3:** Team members can use a single client to access both the primary team channel as well as IRC channels
## Suggestions
* There is a rocketchat-irc bridge solution (okurz has that, not perfect, personal instance, could have some limitations, e.g. I think messages that I write myself from RC are not mirrored in IRC so I try to avoid that :))
* coolo proposed: "if that [rocketchat-irc bridge] works, can we close *qa-tools* on irc.suse.de in favor of *#openqa* and *#openqa-dev*? I find 3 channels a little hard for just one topic
* use *#openqa-dev (RC)* for the team to focus dev talk from support (invite-only)
* *#testing (RC)* could be enough as a support channel with *#testing (IRC)* and *#suse (RC)* and *#suse (IRC)* as fallback, e.g. for people not involved in QA to ask
* AGREED: close *#openqa (RC)*, never had real traffic
* close *#qa-tools (IRC)*