Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #12780

Re: Contacting Java packaging team

Show all headers | View raw

Hi Emmanuel,

Am Tue, Jun 25, 2024 at 11:06:59PM +0200 schrieb Emmanuel Bourg:
> > The problems Pierre described with upgrading Gradle might be some
> > indication that some more skilled packagers could help.
> 
> We would need a core Gradle and/or Kotlin developer to tackle this issue,
> but I don't think they are interested in spending days or weeks figuring out
> an upgrade path for old versions of Gradle.

I don't have the slightest idea about the technical details but I've
seen good cooperation for instance to get bazel packaged and other
fruitful cooperations with upstream.  Finally I do not think it is good
if Debian is lagging behind gradle upstream more and more and we somehow
need to catch up.  IMHO at least we should try and if I can help out
to establish this contact as DPL I'd happily help here.
 
> > I intentionally linked to some response I once received[2] which says:
> > "java-team have pipelines disabled by default".  I consider this a
> > really unfortunate blocker to simply switch on Salsa CI.  If there is no
> > policy to use Salsa CI or not please make sure developers will not need
> > extra hurdles to switch it on.
> 
> If I remember well, the repository creation script [1] for the Java team
> disables the CI feature, because at the time it was written the Salsa CI
> wasn't implemented yet.
 
I can only say that java-team is the only team space I know with this
extra hard setting to switch on Salsa-CI.  If you are willing to change
this but have no idea how this can be done I'd volunteer to find out the
needed information.
 
> > Regarding the "IRC spam":  IMHO this is not a Salsa CI feature but
> > rather the KGB bot you can switch of.
> 
> I'd like KGB to report commits but not CI builds, if that's possible.

Usually these things are configurable.  I have no idea how but if this
is your main reason to not enable Salsa CI I would also try to find this
information.
 
> > For me as someone who barely
> > speaks any Java and just crossing fingers that the upstream build system
> > works flawlessly it helps a lot to have some build log available online
> > very easily which I can link to in some mail to the Debian Java list to
> > get further help.  This might be true for potential newcomers as well.
> 
> That's indeed a convenience, but with an energy cost and a CO2 impact on the
> planet.

I've heard that CO2 saving argument in connection with Salsa CI.  As you
might have read in my platform I personally care for the environment.
In this regard its really hard to draw a line.  You could argue that we
should not support old, power hungry architectures, stop this or that
service etc.  I do not consider the discussion on that level as fruitful.

Kind regards
    Andreas.

> [1] https://salsa.debian.org/java-team/pkg-java-scripts/-/blob/master/setup-salsa-repository

-- 
https://fam-tille.de

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Find similar

Thread

Contacting Java packaging team Andreas Tille <tille@debian.org> - 2024-06-12 17:30 +0200
  Re: Contacting Java packaging team Emmanuel Bourg <ebourg@apache.org> - 2024-06-16 22:50 +0200
    Re: Contacting Java packaging team Mechtilde <ooo@mechtilde.de> - 2024-06-17 07:40 +0200
    Re: Contacting Java packaging team Andreas Tille <tille@debian.org> - 2024-06-17 08:20 +0200
      Re: Contacting Java packaging team Emmanuel Bourg <ebourg@apache.org> - 2024-06-25 23:10 +0200
        Re: Contacting Java packaging team gregor herrmann <gregoa@debian.org> - 2024-06-25 23:40 +0200
        Re: Contacting Java packaging team Andreas Tille <tille@debian.org> - 2024-06-26 11:00 +0200

csiph-web