Reading through #community > Infrastructure & Operations Working Group @ ๐ฌ makes me wonder if we should have an #ops channel. Or #infra or whatever @Deirdre Kirmis and @Oliver Bertuch and others what to call it. What do you think?
Dunno. We kind of have ct and troubleshoot, which both are involved in ops. Where are people supposed to go? How do we scope the channels? Would it make sense to rename one and widen scope of an existing?
maaaaybe
Don't get me wrong: I'd love a place for this. It felt weird to place the KMS/Bao stuff in troubleshoot...
We could probably even move a few interesting, older topics there.
As our list of channels is ever growing, should we add a welcome message and explain what goes where? Maybe have a little something some place else like on gdcc.io? https://zulip.com/help/configure-a-custom-welcome-message
Just trying to avoid too much confusion for users looking at the channels, having no idea where to go and then stepping back from asking because they feel a chance of picking the "wrong" place.
Oh and want could put more text on chat.dataverse.org!
The troubleshooting and containers channels are the largest channels in the list, really much larger than the others, so it may make sense to divide them out a bit .. specifically to have a channel dedicated to infra/app installation, configuration and operations. I guess that would be my preference but curious what others think.
A new channel sound fine to me. What should we call it? #ops? #infra? #sysadmin?
#infra-ops? #sysops? #infra-sysops? Or really I guess just #ops would work as it matches #dev .. but may not be as clear .. my vote is for #infra-ops
#infra-ops would certainly map well to "Infrastructure & Operations Working Group", the group you proposed.
Last updated: Aug 18 2026 at 08:27 UTC