Re-Launching the Java SIG

[Fabio Valentini]

This past weekend I finally decided to jump off the cliff and attempt
to re-launch the Java SIG. It seems there's some interest in keeping
the Java stack maintained, it's just not focused or organized right
now.

What we did when starting the Stewardship SIG seems to have worked out
pretty well, so I'm trying to follow in those footsteps here:

- new proper FAS / pkgdb group: java-maint-sig ("java-sig" is occupied
by an old, unused bot account)
- new private mailing list: java-maint-sig (for RHBZ bugs - so,
possibly, also CVEs - hence, private)
- tracking project on pagure: https://pagure.io/java-maint-sig (for
maintenance scripts, tracking tickets, awesome package dashboards,
etc.)

There's already a public fedora mailing list for Java (java-devel),
and and IRC channel (#fedora-java on freenode.net), which we will
continue to use. Sadly, the existing wiki page for the Java SIG is
hopelessly outdated, so I'm tempted to just scrap it and point readers
to the pagure tracking project once it's set up beyond a basic README
file.

Major upcoming projects for the "new" Java Package Maintainers group include:

- managing OpenJDK 11 / Java 11 transition for hundreds of Java
packages in fedora 33
- starting to transition well-maintained Java packages from the
Stewardship SIG back into Java SIG
- possibly porting packages from gradle to maven to fix build issues
and broken dependencies
- transitioning from old java.net / JavaEE projects to the new ones
now under the eclipse-ee4j umbrella

I know that - among others - the PKI team, Neuro SIG, and Eclipse
maintainers depend on parts of the java stack for their packages, so I
hope that we can work together with them on these things, as well.

So, if you're interested, please consider joining this group effort.
I'll get new members set up with the FAS group / pagure project / mailing list.

Let's make this happen.
Fabio

[Aleksandar Kurtakov]

On Mon, May 11, 2020 at 10:46 PM Fabio Valentini <decathorpe(a)gmail.com&gt;
wrote:

>  This past weekend I finally decided to jump off the cliff and
> attempt
>  to re-launch the Java SIG. It seems there's some interest in keeping
>  the Java stack maintained, it's just not focused or organized right
>  now.
>
>  What we did when starting the Stewardship SIG seems to have worked out
>  pretty well, so I'm trying to follow in those footsteps here:
>
>  - new proper FAS / pkgdb group: java-maint-sig ("java-sig" is occupied
>  by an old, unused bot account)
>  - new private mailing list: java-maint-sig (for RHBZ bugs - so,
>  possibly, also CVEs - hence, private)
>  - tracking project on pagure: https://pagure.io/java-maint-sig (for
>  maintenance scripts, tracking tickets, awesome package dashboards,
>  etc.)
>
>  There's already a public fedora mailing list for Java (java-devel),
>  and and IRC channel (#fedora-java on freenode.net), which we will
>  continue to use. Sadly, the existing wiki page for the Java SIG is
>  hopelessly outdated, so I'm tempted to just scrap it and point readers
>  to the pagure tracking project once it's set up beyond a basic README
>  file.
>
>  Major upcoming projects for the "new" Java Package Maintainers group
>  include:
>
>  - managing OpenJDK 11 / Java 11 transition for hundreds of Java
>  packages in fedora 33
>  - starting to transition well-maintained Java packages from the
>  Stewardship SIG back into Java SIG
>  - possibly porting packages from gradle to maven to fix build issues
>  and broken dependencies
>  - transitioning from old java.net / JavaEE projects to the new ones
>  now under the eclipse-ee4j umbrella
>
>  I know that - among others - the PKI team, Neuro SIG, and Eclipse
>  maintainers depend on parts of the java stack for their packages, so I
>  hope that we can work together with them on these things, as well.
>
>  So, if you're interested, please consider joining this group effort.
>  I'll get new members set up with the FAS group / pagure project / mailing
>  list.
>  
Good luck with that! As someone that has been part of the Java SIG since
day 0 I wish you make Fedora even better workstation for Java developer
than we ever managed.


>  Let's make this happen.
>  Fabio
>  _______________________________________________
>  java-devel mailing list -- java-devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to java-devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]...
>  

-- 
Alexander Kurtakov
Red Hat Eclipse Team

[Severin Gehwolf]

On Mon, 2020-05-11 at 21:45 +0200, Fabio Valentini wrote:
>  This past weekend I finally decided to jump off the cliff and
> attempt
>  to re-launch the Java SIG. It seems there's some interest in keeping
>  the Java stack maintained, it's just not focused or organized right
>  now.
>  
>  What we did when starting the Stewardship SIG seems to have worked
>  out
>  pretty well, so I'm trying to follow in those footsteps here:
>  
>  - new proper FAS / pkgdb group: java-maint-sig ("java-sig" is
>  occupied
>  by an old, unused bot account)
>  - new private mailing list: java-maint-sig (for RHBZ bugs - so,
>  possibly, also CVEs - hence, private)
>  - tracking project on pagure: https://pagure.io/java-maint-sig (for
>  maintenance scripts, tracking tickets, awesome package dashboards,
>  etc.)
>  
>  There's already a public fedora mailing list for Java (java-devel),
>  and and IRC channel (#fedora-java on freenode.net), which we will
>  continue to use. Sadly, the existing wiki page for the Java SIG is
>  hopelessly outdated, so I'm tempted to just scrap it and point
>  readers
>  to the pagure tracking project once it's set up beyond a basic README
>  file.
>  
>  Major upcoming projects for the "new" Java Package Maintainers group
>  include:
>  
>  - managing OpenJDK 11 / Java 11 transition for hundreds of Java
>  packages in fedora 33
>  - starting to transition well-maintained Java packages from the
>  Stewardship SIG back into Java SIG
>  - possibly porting packages from gradle to maven to fix build issues
>  and broken dependencies
>  - transitioning from old java.net / JavaEE projects to the new ones
>  now under the eclipse-ee4j umbrella
>  
>  I know that - among others - the PKI team, Neuro SIG, and Eclipse
>  maintainers depend on parts of the java stack for their packages, so
>  I
>  hope that we can work together with them on these things, as well.
>  
>  So, if you're interested, please consider joining this group effort.
>  I'll get new members set up with the FAS group / pagure project /
>  mailing list.
>  
>  Let's make this happen. 
Thanks Fabio!

I'll be happy to join and will try to liaise as we continue to look
after the OpenJDK packages themselves.

Cheers,
Severin

I would like to be a part of the Fedora Java SIG. I already have a FAS
account setup and am a Silverblue and Fedora Magazine contributor, as
well as moderator on discussion/fedoraproject.org and
start.fedoraproject.org.

Regards,
Stephen Snow (jakfrost)

On Mon, 2020-05-11 at 21:45 +0200, Fabio Valentini wrote:
>  This past weekend I finally decided to jump off the cliff and
> attempt
>  to re-launch the Java SIG. It seems there's some interest in keeping
>  the Java stack maintained, it's just not focused or organized right
>  now.
>  
>  What we did when starting the Stewardship SIG seems to have worked
>  out
>  pretty well, so I'm trying to follow in those footsteps here:
>  
>  - new proper FAS / pkgdb group: java-maint-sig ("java-sig" is
>  occupied
>  by an old, unused bot account)
>  - new private mailing list: java-maint-sig (for RHBZ bugs - so,
>  possibly, also CVEs - hence, private)
>  - tracking project on pagure: https://pagure.io/java-maint-sig (for
>  maintenance scripts, tracking tickets, awesome package dashboards,
>  etc.)
>  
>  There's already a public fedora mailing list for Java (java-devel),
>  and and IRC channel (#fedora-java on freenode.net), which we will
>  continue to use. Sadly, the existing wiki page for the Java SIG is
>  hopelessly outdated, so I'm tempted to just scrap it and point
>  readers
>  to the pagure tracking project once it's set up beyond a basic README
>  file.
>  
>  Major upcoming projects for the "new" Java Package Maintainers group
>  include:
>  
>  - managing OpenJDK 11 / Java 11 transition for hundreds of Java
>  packages in fedora 33
>  - starting to transition well-maintained Java packages from the
>  Stewardship SIG back into Java SIG
>  - possibly porting packages from gradle to maven to fix build issues
>  and broken dependencies
>  - transitioning from old java.net / JavaEE projects to the new ones
>  now under the eclipse-ee4j umbrella
>  
>  I know that - among others - the PKI team, Neuro SIG, and Eclipse
>  maintainers depend on parts of the java stack for their packages, so
>  I
>  hope that we can work together with them on these things, as well.
>  
>  So, if you're interested, please consider joining this group effort.
>  I'll get new members set up with the FAS group / pagure project /
>  mailing list.
>  
>  Let's make this happen.
>  Fabio
>  _______________________________________________
>  java-devel mailing list -- java-devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to 
>  java-devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: 
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail]...

[Markku Korkeala]

On 5/11/20 10:45 PM, Fabio Valentini wrote:
>  This past weekend I finally decided to jump off the cliff and
> attempt
>  to re-launch the Java SIG. It seems there's some interest in keeping
>  the Java stack maintained, it's just not focused or organized right
>  now 
Great, really appreciate your work.

>  
>  So, if you're interested, please consider joining this group effort.
>  I'll get new members set up with the FAS group / pagure project / mailing list.
Count me in! I'm relatively new to fedora and rpm packaging, but got ~20
years of working with Java and my packages depends on the Java
ecosystem. FAS account: korkeala.

Markku.



>  Let's make this happen.
>  Fabio
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>

[Igor Raits]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Mon, 2020-05-11 at 21:45 +0200, Fabio Valentini wrote:
>  This past weekend I finally decided to jump off the cliff and
> attempt
>  to re-launch the Java SIG. It seems there's some interest in keeping
>  the Java stack maintained, it's just not focused or organized right
>  now.
>  
>  What we did when starting the Stewardship SIG seems to have worked
>  out
>  pretty well, so I'm trying to follow in those footsteps here:
>  
>  - new proper FAS / pkgdb group: java-maint-sig ("java-sig" is
>  occupied
>  by an old, unused bot account)
>  - new private mailing list: java-maint-sig (for RHBZ bugs - so,
>  possibly, also CVEs - hence, private)
>  - tracking project on pagure: https://pagure.io/java-maint-sig (for
>  maintenance scripts, tracking tickets, awesome package dashboards,
>  etc.)
>  
>  There's already a public fedora mailing list for Java (java-devel),
>  and and IRC channel (#fedora-java on freenode.net), which we will
>  continue to use. Sadly, the existing wiki page for the Java SIG is
>  hopelessly outdated, so I'm tempted to just scrap it and point
>  readers
>  to the pagure tracking project once it's set up beyond a basic README
>  file.
>  
>  Major upcoming projects for the "new" Java Package Maintainers group
>  include:
>  
>  - managing OpenJDK 11 / Java 11 transition for hundreds of Java
>  packages in fedora 33
>  - starting to transition well-maintained Java packages from the
>  Stewardship SIG back into Java SIG
>  - possibly porting packages from gradle to maven to fix build issues
>  and broken dependencies
>  - transitioning from old java.net / JavaEE projects to the new ones
>  now under the eclipse-ee4j umbrella
>  
>  I know that - among others - the PKI team, Neuro SIG, and Eclipse
>  maintainers depend on parts of the java stack for their packages, so
>  I
>  hope that we can work together with them on these things, as well.
>  
>  So, if you're interested, please consider joining this group effort.
>  I'll get new members set up with the FAS group / pagure project /
>  mailing list. 
Count me in! I don't think I can help much, but at least can give some
suggestions.

>  Let's make this happen. 
Good luck, Fabio!

>  Fabio
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: 
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: 
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives: 
>  https://lists.fedoraproject.org/archives/list/[e-mail] 
- -- 
Igor Raits <ignatenkobrain(a)fedoraproject.org&gt;
> -----BEGIN PGP SIGNATURE-----
>
> iQIzBAEBCgAdFiEEcwgJ58gsbV5f5dMcEV1auJxcHh4FAl66y7cACgkQEV1auJxc
> Hh43Gg/+NzTe/eeGyuWQnKkPwiImM0wgg3ZUEMftfURWLFLpK3zNYBK1jH2hNKHY
> VA7d3NB4DhTtDAwQUVtFCmcfTuoLpZeKvvlaK5T8z0jIRqBEaHJx8NAqQFhnYw0q
> NGjvogdsQMW1uFbnBJrxD3o2CIXwonmE4va204vOLMybF+jSw/1s6GlLVZgX6PsL
> lSGIfmYWyf5UVUUwhP4zfzKZy56EEIOVjN+gq0ZdywPQyEfz+lpbKsBdCjL/Gwf7
> wMJm0Y+tO/J/jyeTQ7WPnJUbwL6YHcb+iDOSZqGBvfxp8bRa7k3lFbKdgKZzV+hs
> 5q9xYlNatpaH+axMwpBvDch31yZ7OemFxv39Kx70LP+HZqKYokDR8MNQr80bIynt
> jSa11wxzmOu5QjQJclORVdik/KsdjL/2MHCA4tFj/NFWQz2lIDX1wMCxIvmTyz3O
> NsOLGT/Cc8ZfFCCMnC/i0TtUcyytNurB9t4CK8RzwNeqVT7VeeZs+q/OHjlsedA5
> orooA6ovd9B+w7hajlvn/cdvWVFuAq3GYZm/DQaaklZCSxYpBZrUYxS3tJbmOqhR
> 4gch4aQoiLWEKUeV/G52UvRfky0B1ke7d7w3mscBB+43/Vxlsps4/PT1yt7/psNX
> gwrVyfplA15ZRcoXB8HVimzCV9YownNcHAFdtNBdt3Aq3/UADpk=
> =jv6E
> -----END PGP SIGNATURE-----