The docs team organizes themselves in #docs in Project Discussion, using topics with #docs in there to discuss what they have to discuss (excluding weekly meetings on Matrix that are prepared and later summed up on #docs in Project Discussion). If I have an issue that is related to Docs, and I know about the Docs relation / implication (I think that is the condition you talk about when it comes to someone asking about fedora-ci or give feedback about it), I do the same: I use the #docs tag of Project Discussion to ask and discuss the issue with the team. Sometimes it brings up something new, sometimes I am just answered why something is in Docs the way it is and how to get something done (e.g., how to adjust an article in a specific way, or why I have to do it in a certain way, etc.).
Unless you expect massive amounts of topics, I assume the #fedora-ci should do the trick in Project Discussion. Not sure if I misunderstood something?
Yes, indeed the parallel with #docs works well for the purpose of this. The only addition is that some announcements will also be posted there, but that would probably be the same in these as well.
. I do hope there would not be massive amounts of topics or long discussion threads
Well, within the rules of Discourse, a team is free how it uses its tags. The Docs team also has a weekly topic announcing the meeting To Do list, and later its summary. So announcements for the team and those who follow it are nothing new in such a scope.
Keep in mind that tags can be subscribed to, etc. (so people subscribe to the tag, and can decide themselves if they want to get an email if any new topic/thread is created with that tag, or alternatively both when new topics are opened with the tag AND any post within any of these topics, etc.)