nodejs-array-uniq needs new permanent maintainer(s)
by Fabio Valentini
Hello packagers,
The Stewardship SIG is currently providing only bare-minimum
maintenance for the nodejs-array-uniq 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 nodejs-array-uniq or
maintains a package that depends on it.
For reference, the following packages have a direct dependency on
nodejs-array-uniq, either at build- or at install-time:
- nodejs-gulp-util
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 nodejs-array-uniq.
If you want to take nodejs-array-uniq 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
4 years, 12 months
nodejs-array-union needs new permanent maintainer(s)
by Fabio Valentini
Hello packagers,
The Stewardship SIG is currently providing only bare-minimum
maintenance for the nodejs-array-union 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 nodejs-array-union or
maintains a package that depends on it.
For reference, the following packages have a direct dependency on
nodejs-array-union, either at build- or at install-time:
- nodejs-globby
- nodejs-multimatch
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 nodejs-array-union.
If you want to take nodejs-array-union 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
4 years, 12 months
apache-commons-discovery needs new permanent maintainer(s)
by Fabio Valentini
Hello packagers,
The Stewardship SIG is currently providing only bare-minimum
maintenance for the apache-commons-discovery 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
apache-commons-discovery or maintains a package that depends on it.
For reference, the following packages have a direct dependency on
apache-commons-discovery, either at build- or at install-time:
- eclipse-webtools
- jenkins
- jenkins-commons-jelly
- mx4j
- stapler
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 apache-commons-discovery.
If you want to take apache-commons-discovery 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
4 years, 12 months
