On Wed, May 22, 2019 at 5:56 PM Fabio Valentini <decathorpe(a)gmail.com> wrote:
Hello packagers,
The Stewardship SIG is currently providing only bare-minimum
maintenance for the glassfish-jsp package, and none of our packages
depend on it. So, we're looking for someone to take better care of it,
preferably someone who actively uses glassfish-jsp or maintains a
package that depends on it.
For reference, the following packages have a direct dependency on
glassfish-jsp, either at build- or at install-time:
- eclipse
- hadoop
- jspc
If you received this email directly, you're a (co-)maintainer of one
of these packages, and would probably be best qualified to take care
of glassfish-jsp.
If you want to take glassfish-jsp off our hands, fill out the
"package_adoption_request" template here:
https://www.pagure.io/stewardship-sig/new_issue
If nobody claims the package within the next two weeks, we will orphan
it again, setting it on its course towards retirement in about two
months.
Thanks,
Fabio (decathorpe), for the Stewardship SIG
It seems to me that the steady flow of orphaning happening by the
Stewardship SIG is not much better than the previous mass orphaning,
especially for casual packagers who depend on these. I understand the
Stewardship SIG can't maintain these indefinitely, but I was kinda
hoping for at least one or two Fedora releases... to have enough time
to come to terms with the missing deps and to try to understand
modularity. At the current rate, it seems we're still headed for mass
orphaning and/or many one-package-each modules in the near future.