On Thu, Jun 18, 2020 at 6:50 PM Ben Rosser <rosser.bjr(a)gmail.com> wrote:
Hi Fabio,
I'm not sure how much time I'll be able to put in, but I'd be very
happy to (help) work on this, either as part of the Stewardship or
Nodejs SIGs, or both. Hopefully others interested in the nodejs
ecosystem (Sérgio and Jared, perhaps?) would be willing to consider
helping too.
The Nodejs SIG does have ACLs on (almost?) all of these packages, and
I know there are at least a few active packagers there, so hopefully
they would be willing to help as well. I think the immediate problem
is figuring out what in this large stack of nodejs packages is
actually useful (and stopping them from being retired in a week and a
half), so being able to use the tooling you mentioned would be very
helpful, I think. Then we'd need to ultimately find new
points-of-contact for the useful ones (while allowing the non-useful
ones to be retired); in the long term, I'd be willing to pick up some
of those (hopefully not all, but who knows).
How does one go about joining the Stewardship SIG?
Hi Ben,
I think the situation for the NodeJS SIG is a bit different, since it
already has a group for organizing dist-git access, we didn't have
that for the Java stack, so we needed a new FAS group. I think it
should be possible to adapt our tooling for the purposes of the
nodejs-sig.
The scripts and tooling we use to make maintenance easier for us are
in this git repo:
https://github.com/fedora-stewardship/fedora-stewardship.github.io
It should be pretty straightforward to adapt some scripts (especially
./sig_report.py and ./check_sig_leaf.py) - I think changing the string
"stewardship-sig" for "nodejs-sig" should be enough in most cases :)
The page with reports and statistics that's generated with those
scripts is online here:
https://fedora-stewardship.github.io/
Maybe it can serve as inspiration for the nodejs-sig.
Fabio