On Thu, May 23, 2019, 01:01 Christopher <ctubbsii@apache.org> wrote:
On Wed, May 22, 2019 at 5:56 PM Fabio Valentini <decathorpe@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

Hi Christopher,


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.

We never promised more than a "life extension" for these packages. The SIG can act as glue so that the foundation other packagers depend on doesn't crumble over night. But if the foundations don't settle and these packages get permanent maintainers, glue won't be enough to keep it together.

I understand the
Stewardship SIG can't maintain these indefinitely, but I was kinda
hoping for at least one or two Fedora releases...

*Two* fedora releases? That's a bit optimistic.

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.

No. I outlined the procedure were following multiple times, and at the current rate, it will take 1-2 years to go through all our packages. So actually, for packages deeper in the stack, 2 years isn't so optimistic after all.


It's just that we started the cleanup procedure at the top of the stack, and you're affected by that already.

Fabio