Hi Emmanuel,
Le 2025-07-22 à 12 h 25, Emmanuel Bourg a écrit :
Hi Jérôme,
On 19/07/2025 11:36, Jérôme Charaoui wrote:
Does that work for everyone?
I'm the one who implemented IRC notifications on debian-java a few years
ago, based on the work done for other Debian channels at this time. I
personally find it interesting to have push notifications on the
channel, because it can trigger discussions/reviews about the changes
being done and bring more life to a mostly dormant channel.
Right, I think the concern for keeping the channel alive a valid point.
However before changing things up again I'd like to try and see how
things go. Let's review this at a future java-team meeting that we
agreed to hold on a regular basis! :)
Some time later we started getting CI/pipeline notifications through the
same mechanism, and it became way to verbose in my opinion.
Indeed. But those CI notification were the default in the
"setup-salsa-repository" script since it creation. I think there are
just more packages that enabled CI pipelines in the meantime.
I think we should keep the notifications, but only for pushes (ideally
one line per branch pushed, not one line per commit). We could also
filter the notifications related to the pristine-tar branch. And CI/
pipeline notifications should be blocked (or moved to another channel
nobody will follow).
In GitLab, each commit pushed to a tree is considered a "push event", so
it's not possible to generate a single notification for a single "git
push" command used by a repo maintainer (unless a single commit is
sent). This is why for example when a rebased branch is pushed, there
can be many commit notifications.
I'm not on IRC these days, so this is merely a recommendation, feel free
to adjust the configuration as you like.
Thanks! Don't hesitate to visit sometime :)
-- Jérôme
