Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: =?UTF-8?B?SsOpcsO0bWUgQ2hhcmFvdWk=?= Newsgroups: linux.debian.maint.java Subject: Re: Java team IRC channel Date: Tue, 22 Jul 2025 20:30:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-java-request@lists.debian.org Tue Jul 22 18:27:35 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.896 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -4.6 X-Riseup-User-ID: 137BE822A84531D9F2BFC71F0094CC36977228614D5CE57F8097A3B718209466 MIME-Version: 1.0 Content-Language: fr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/23761 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/96fd4754-b00e-49d6-b400-ed1893ecbccb@riseup.net Approved: robomod@news.nic.it Lines: 45 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 22 Jul 2025 14:27:16 -0400 X-Original-Message-ID: <96fd4754-b00e-49d6-b400-ed1893ecbccb@riseup.net> X-Original-References: Xref: csiph.com linux.debian.maint.java:13029 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