Hello,

At the moment the #debian-java channel is much less useful than it could
be because of the high number of Salsa notifications that are sent to
it. These notifications are also quite bursty: in between periods of
quiet time, there could be several dozen notifications printed to the
channel in a short time span.

So, as I mentioned during today's DebConf Java-team BoF meeting, I'd
like to propose moving *all* Salsa notifications for java-team projects
to a new channel: #debian-java-changes

- All branches
- Push, tag and MR events only

I would also like to propose adding Debian's Java packages to the BTS
bot [1] on IRC, to post BTS and archive notifications to
#debian-java-changes as well.

This is akin to what other teams are doing in Debian.

I believe this change will help make the IRC channel useful again for
mutual help and onboarding newcomers to the Debian Java packaging world.

Does that work for everyone?

Thanks.

[1] https://github.com/sebastinas/debian-devel-changes-bot

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------lyYenHJ0qLfmT3rBpXAzBr7X
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

Rm9yIG1lICsxDQoNCkFtIDE5LjA3LjI1IHVtIDExOjM2IHNjaHJpZWIgSsOpcsO0bWUgQ2hh cmFvdWk6DQo+IEhlbGxvLA0KPiANCj4gQXQgdGhlIG1vbWVudCB0aGUgI2RlYmlhbi1qYXZh IGNoYW5uZWwgaXMgbXVjaCBsZXNzIHVzZWZ1bCB0aGFuIGl0IGNvdWxkIA0KPiBiZSBiZWNh dXNlIG9mIHRoZSBoaWdoIG51bWJlciBvZiBTYWxzYSBub3RpZmljYXRpb25zIHRoYXQgYXJl IHNlbnQgdG8gDQo+IGl0LiBUaGVzZSBub3RpZmljYXRpb25zIGFyZSBhbHNvIHF1aXRlIGJ1 cnN0eTogaW4gYmV0d2VlbiBwZXJpb2RzIG9mIA0KPiBxdWlldCB0aW1lLCB0aGVyZSBjb3Vs ZCBiZSBzZXZlcmFsIGRvemVuIG5vdGlmaWNhdGlvbnMgcHJpbnRlZCB0byB0aGUgDQo+IGNo YW5uZWwgaW4gYSBzaG9ydCB0aW1lIHNwYW4uDQo+IA0KPiBTbywgYXMgSSBtZW50aW9uZWQg ZHVyaW5nIHRvZGF5J3MgRGViQ29uZiBKYXZhLXRlYW0gQm9GIG1lZXRpbmcsIEknZCANCj4g bGlrZSB0byBwcm9wb3NlIG1vdmluZyAqYWxsKiBTYWxzYSBub3RpZmljYXRpb25zIGZvciBq YXZhLXRlYW0gcHJvamVjdHMgDQo+IHRvIGEgbmV3IGNoYW5uZWw6ICNkZWJpYW4tamF2YS1j aGFuZ2VzDQo+IA0KPiAtIEFsbCBicmFuY2hlcw0KPiAtIFB1c2gsIHRhZyBhbmQgTVIgZXZl bnRzIG9ubHkNCj4gDQo+IEkgd291bGQgYWxzbyBsaWtlIHRvIHByb3Bvc2UgYWRkaW5nIERl YmlhbidzIEphdmEgcGFja2FnZXMgdG8gdGhlIEJUUyANCj4gYm90IFsxXSBvbiBJUkMsIHRv IHBvc3QgQlRTIGFuZCBhcmNoaXZlIG5vdGlmaWNhdGlvbnMgdG8gI2RlYmlhbi1qYXZhLSAN Cj4gY2hhbmdlcyBhcyB3ZWxsLg0KPiANCj4gVGhpcyBpcyBha2luIHRvIHdoYXQgb3RoZXIg dGVhbXMgYXJlIGRvaW5nIGluIERlYmlhbi4NCj4gDQo+IEkgYmVsaWV2ZSB0aGlzIGNoYW5n ZSB3aWxsIGhlbHAgbWFrZSB0aGUgSVJDIGNoYW5uZWwgdXNlZnVsIGFnYWluIGZvciANCj4g bXV0dWFsIGhlbHAgYW5kIG9uYm9hcmRpbmcgbmV3Y29tZXJzIHRvIHRoZSBEZWJpYW4gSmF2 YSBwYWNrYWdpbmcgd29ybGQuDQo+IA0KPiBEb2VzIHRoYXQgd29yayBmb3IgZXZlcnlvbmU/ DQo+IA0KPiBUaGFua3MuDQo+IA0KPiBbMV0gaHR0cHM6Ly9naXRodWIuY29tL3NlYmFzdGlu YXMvZGViaWFuLWRldmVsLWNoYW5nZXMtYm90DQo+IA0KDQotLSANCk1lY2h0aWxkZSBTdGVo bWFubg0KIyMgRGViaWFuIERldmVsb3Blcg0KIyMgUEdQIGVuY3J5cHRpb24gd2VsY29tZQ0K IyMgRjBFMyA3RjNEIEM4N0EgNDk5OCAyODk5ICAzOUU3IEYyODcgN0JCQSAxNDFBIEFEN0YN
Cg0K

--------------lyYenHJ0qLfmT3rBpXAzBr7X--

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAmh7bL8ACgkQ8od7uhQa rX/KCg//UlPDJwCTQ3vr4Ocs8dVU5YCjRxN30NUoGhLg6pLQ9LNtDFTQHgU/iDfY mKfk5s9Eu9Os+uRUCPPg4En1r8XMoedBjlECh4JnwjYnB1SNfwDAuPQ6B5zum1/3 M6xo1aZ/zchsmw+aS61T3A0FC6ifYv3RiSSPuDkGP9ZLYzioAls5PJc4yrUTQRn8 X4z7Wn5xIE0TIcAkeyy902UL25BfV72euSMGQ4yEUQtOuzgSsfs3BfmeyxrEXoRB 4QADyNjft9/o7Qu2wDcaE54LchyA9DqXt8jzFAG4CVaEk45LuDJ79ELUw2iHT0we 3ZieNOo6G74PznZ7ka+YMBN+iJKBoK3wv20dEfRRLGZOugY4tD4JtBT1P5IWjpAl b4iUrMpsLyeT8x7jlWz2sZFK0uCDZ1peaGgsXy5OpUcjli1uEx3N1YkEuDy1L6CX XvS+HzPF+bNs+ipUfij3VHzGHOAw/bXSzBGnqJxbqxTD5vHphYf8MPbjakZh4BIn bt7/f03FvSTAGrzm+A8lbpner37+fNkPEC2szZVQ/LTTA8OfrKuCpyh4jsoZifMt 9WgK/q3NYu+fTE3wYR0ZgXfzB8KI98iFy36/WF1METkhjzLGrHu6pA7lrDqHZ/jT q47jMjQrl3wgY6M+IxIlH0WmZSmNfNHQeqo9bazAMs2DO6xXnPg=
=RQ27
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Jul 19, 2025 at 11:36:43AM +0200, Jérôme Charaoui wrote:

I would also like to propose adding Debian's Java packages to the BTS
bot [1] on IRC, to post BTS and archive notifications to
#debian-java-changes as well.

This is akin to what other teams are doing in Debian.

I believe this change will help make the IRC channel useful again for
mutual help and onboarding newcomers to the Debian Java packaging world.

Does that work for everyone?

Yes, and thank you!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 2025-07-21 à 10 h 55, tony mancill a écrit :

On Sat, Jul 19, 2025 at 11:36:43AM +0200, Jérôme Charaoui wrote:

I would also like to propose adding Debian's Java packages to the BTS
bot [1] on IRC, to post BTS and archive notifications to
#debian-java-changes as well.

This is akin to what other teams are doing in Debian.

I believe this change will help make the IRC channel useful again for
mutual help and onboarding newcomers to the Debian Java packaging world.

Does that work for everyone?

Yes, and thank you!

Thanks for the positive feedback: I've now implemented the changes.

To all: if you've ever tried to get involved on the team via the
#debian-java IRC channel, please try again now. It should be much more
serene and conducive to collaboration and discussion!

If you're interested in keeping an eye on the Java package ecosystem in
Debian, I invite you to join #debian-java-changes where notifications
about commits, pushes, uploads and bugs will now be posted.

Cheers,

-- Jérôme

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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.

Some time later we started getting CI/pipeline notifications through the
same mechanism, and it became way to verbose in my opinion.

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).

I'm not on IRC these days, so this is merely a recommendation, feel free
to adjust the configuration as you like.

Emmanuel Bourg

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)