I would also create a cassandra-tickets channel and move it there. I also consider cassandra-noise too noisy already for that.
On Wed, Sep 24, 2025 at 1:09 AM C. Scott Andreas <[email protected]> wrote: > I actually have QBot notifications starred so new tickets show up on my > phone's lock screen when they're created. I can find other ways to solve > that problem though. :) > > #cassandra-tickets works for me if it's too noisy in dev. > > – Scott > > On Sep 23, 2025, at 3:28 PM, Ekaterina Dimitrova <[email protected]> > wrote: > > > At first, I had similar thoughts as you, Mick, but then I thought that I > would still want to see when some old ticket is getting attention. Not sure > how to get something in between cassandra-noise and the newly suggested > cassandra-tickets. > > Maybe Bernardo is into something, daily updates sounds tempting. Even just > to say which tickets were updated/created/closed. I am curious to hear more > about the mentioned prototype. > > Best regards, > Ekaterina > > On Tue, 23 Sep 2025 at 17:59, Mick <[email protected]> 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? >> >> >> > >
