Seems we have a pretty clear consensus (on a low stakes thing). What are next steps?
Brandon - you have the connections and/or permissions to: 1. Remove Qbot JIRA create/close from #cassandra-dev, and 2. Create a #cassandra-tickets channel that has that stream of information ? Or is this a "teach a man to fish" moment? ;) On Wed, Sep 24, 2025, at 6:45 PM, Jindal, Himanshu wrote: > +1 to #cassandra-tickets. > Also +1 to keeping Cassandra-dev human messages only and moving automation to > separate more focused channels like #cassandra-noise, #cassandra-tickets or > #cassandra-jira-summary etc. > > Himanshu > > > *From: *Joseph Lynch <[email protected]> > *Date: *Wednesday, September 24, 2025 at 1:27 PM > *To: *[email protected] <[email protected]> > *Subject: *RE: [EXTERNAL] [DISCUSS] I think Qbot makes the #cassandra-dev > slack channel less useful > *CAUTION*: This email originated from outside of the organization. Do not > click links or open attachments unless you can confirm the sender and know > the content is safe. > > > +1 to a new #cassandra-tickets channel > > On Wed, Sep 24, 2025 at 7:32 AM Jeremiah Jordan <[email protected]> wrote: >> +1 to a new channel with just create and close. I also am in the group of >> people who think #cassandra-noise is too much to follow and appreciate the >> lower volume that is in #cassandra-dev. Perfectly happy to follow that in a >> new channel. That would actually be nice, as you can track you state >> looking over tickets separately from keeping up with conversations. Thanks >> for bringing this up. >> >> -Jeremiah >> >> On Sep 24, 2025 at 8:22:14 AM, Isaac Reath <[email protected]> wrote: >>> +1 to the #cassandra-tickets channel. >>> >>> On Wed, Sep 24, 2025 at 5:04 AM Štefan Miklošovič <[email protected]> >>> wrote: >>>> 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? >>>>>>> >>>>>>> >>>>> >>>>>
