Hmm... I've checked https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ but it doesn't tell me how I need to respond here.

Thanks for your response!

Well, the actions to take depend on what the goal is.

In this case, I'd like to clear up maintenance and ownership - primarily of your Java packages,
which is most of the packages listed here: https://src.fedoraproject.org/user/spike

From what I can tell, you have not touched them in years. Do you want to give other people the chance the pick them up and/or let them get removed from fedora if they're no longer in use?

I'm currently not actively using any of the java related packages you've linked above. I've taken ownership of them back when we renamed the packages from jakarta-* to apache-* and updated them to the latest Java packaging guidelines. But they should all have competent co-maintainers that are way more up to date with the current requirements of the Java packaging guidelines. If you want to take care of the packages, I'm happy to make you co-maintainer or hand them over to you completely to you or one of the existing co-maintainers. I could use some help to get up to speed with the current Java packaging guidelines though if you expect me to fix the current FTBFS issues or update them to the latest version. I'm also completely fine with orphaning them for now.

Well, mizdebsk has done almost no Java packaging in 1.5 years, fnasser also had non-responsive maintainer process activated, and gil and lef have been declared non-responsive over a year ago and all their packages were orphaned (I took most of them). So it's probably sadly no longer true that you have competent co-maintainers :(

From my point of view, the "best" way forward would be for you to orphan your Java packages. If there's any packages in there that the Java SIG still needs, I will take them, and you can stay on as co-maintainer if you want. And the packages that are no longer needed can safely be dropped from fedora.

I've just orphaned the packages you've linked above:

- https://src.fedoraproject.org/rpms/apache-commons-dbcp
- https://src.fedoraproject.org/rpms/apache-commons-parent
- https://src.fedoraproject.org/rpms/apache-commons-validator
- https://src.fedoraproject.org/rpms/geronimo-ejb
- https://src.fedoraproject.org/rpms/joda-time
- https://src.fedoraproject.org/rpms/rmic-maven-plugin

Let me know if I can help with your efforts bringing Java stuff up to snuff.

Thank you!

There's some more packages that need attention, e.g. glassfish-saaj, but basically all glassfish* packages.

Their upstream projects have now moved *twice* (from java.net to github.com/javaee to github.com/eclipse-ee4j) since the demise of java.net, and we've been working on updating them all to their new upstreams and latest versions.
(This is also the reason why no new version bugs were opened for a lot of these packages, since release-monitoring.org wasn't updated to point to the new upstream repos.)

If you want to help with Java packaging, then you're welcome to join the "new" Java SIG and help :)

We have a tracking project for high-level organisation:
https://pagure.io/java-maint-sig

And a kanban board for the nitty-gritty details:
https://teams.fedoraproject.org/project/java-package-maintainer-sig/kanban?kanban-status=471

Let me know if you want to join, I can set up your group membership.

Sign me up! Don't know who much workload I can handle due to $DAYJOB, but if permitted I'd like to lurk and at least re-learn how a Java spec file needs to look like these days. The packaging guidelines look quite a bit different from what they did in 2012.

Great! I've pressed the necessary buttons.
Logging out and back in at src.fedoraproject.org should sync your group membership.

You can look at the packages that are now part of the Java SIG:
https://src.fedoraproject.org/group/java-maint-sig
Most of them are in pretty good shape and up-to-date.

Thanks again for the fast response. I consider this NOTABUG now.