I do agree with this statement. We can also find middle ground with a daily/weekly digester (I have some prototypes for that) if we still want to have some visibility on the dev channel, but I’d rather focus that channel on personal interactions, and try to move as much automated stuff as possible to #cassandra-noise or even specialized channels.
Regards, Bernardo > On Sep 23, 2025, at 11:22 AM, 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?
