On Tue, May 19, 2020 10:44:05 +0200, Fabio Valentini wrote:
<snip>
Good Morning!
We were planning to discuss this from the Stewardship SIG point of
view during today's meeting, and I didn't want to announce any plans
before that.
However, my suggestion would be to do the following things:
1. determine a core set of packages that's required for a functional
java → RPM toolchain
This will include ant, maven, some core maven plugins,
javapackages-tools, xmvn, and all the dependencies of those packages.
2. start moving those packages into the @java-maint-sig
I'd like to do some basic sanity checks when doing that, for example
checking upstream release history, unnecessary dependencies,
possiblitiies to drop unused functionality, etc. Most packages that
are required for building RPMs from Java projects (maven, maven
plugins, plexus-foo, apache-commons-bar, etc.) should already be in
pretty good shape and mostly up-to-date.
3. once that basic set of packages has been moved to the SIG, we can
start looking at which things share Java packages as dependencies
(e.g. glassfish-jaxb is required by both the DogTag PKI team and the
Neuro SIG), and move those to the Java SIG as well, if all parties
want to do that.
---
I'll try coming up with a roadmap for which packages to move first.
I'd like to do this right, so it won't be fast, but I hope we can
improve the Java stack in the process.
Thanks, that sounds great. I look forward to the plan. You're right:
there's no need to hurry. Much better to do it right :)
Unfortunately, I have a work meeting that clashes with the stewardship
SIG meeting, so I won't make it there today. If the work meeting
finishes early, I will pop by to check if the stewardship meeting is
still on.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London