FWIW, my personal experience is that mixing automated notifications
(beyond a very low volume) with human communications adds a bunch of
noise to the human conversations and increases the risk of an
interesting automated notification being missed (scrolling past them to
get to the meatier human conversations).
I'm curious what the argument for pumping ticket notifications into
#cassandra-dev, etc., is, versus pumping them into a dedicated channel.
Thanks -- Joel.
On 4/8/2025 12:51 PM, Ekaterina Dimitrova wrote:
I’d say we mimic the current CASSANDRA tickets handling plus adding to
the #cassandra-sidecar. That means:
1) Open and close notifications to #cassandra-dev and #cassandra-sidecar
2) all other notifications to #cassandra-noise
WDYT?
On Tue, 8 Apr 2025 at 15:48, Josh McKenzie <jmcken...@apache.org> wrote:
Currently we don't have Qbot notifying us on CASSSIDECAR ticket
creation and state change. Seems we could:
1. notify in #cassandra-dev and #cassandra-sidecar
2. notify in the #cassandra-sidecar channel
My preference is for 1 since there's a tight relationship between
what we're doing with the subprojects and the main db and there's
probably shared interest there.
Any other opinions?
