I'm with Mick here, I do find value in seeing the stream of created/ closed tickets. I support having a cassandra-tickets channel to preserve the existing behavior. cassandra-noise will be sufficient for most people, and cassandra-tickets should help other folks that want to have a more concise view of the stream.
Best, - Francisco On 2025/09/23 21:59:00 Mick wrote: > I find cassandra-noise too noisy. > I get value from seeing just the created/closed ticket bot msgs. > But I have no objection to creating another channel just for that, e.g. > cassandra-tickets > > > > > On 23 Sep 2025, at 20:22, Josh McKenzie <[email protected]> wrote: > > > > Subject captures most of it. > > > > The more active our ecosystem gets, the more the slack channel fills up > > with JIRA creation and closing. Since we're async, we regularly have > > discussions that can span multiple days so the "Qbot vs. Human" ratio gets > > pretty bad and discussions get shunted up off the top of the screen. > > > > As a consequence I find myself interfacing with #cassandra-dev less > > frequently since syncing up with what's going on has more friction. I think > > it'd benefit the community to have a place for humans to talk human things > > and then go to the #cassandra-noise channel for more detailed JIRA movement > > updates. > > > > I believe we've discussed this previously but my ponymail searching hasn't > > turned up signal to load up that old context. > > > > So: thoughts? > > >
