-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggested list of modules to help get support info into #413
Comments
@mhdawson Can you please provide some more context here? What am I volunteering for? 😄 |
This has the ask: https://openjsf.org/blog/2020/09/23/node-js-package-maintenance-bridging-the-gap-between-maintainers-and-consumers/ This issue is to track the modules we'd like to prioritize to add support info to. |
I'm going to work getting it added to node-addon-api. We should also make sure to add to all of the modules in pkgjs. |
PR to add support info in node-addon-api -> nodejs/node-addon-api#843 |
The PR to add to node-addon-api landed. Its been added to the modules in github/nodeshift. |
Support info has been added to https://github.com/tj/commander.js |
@shadowspawn thanks ! |
Should we curate a list of packages for us to do outreach to for this, potentially sourced from our list of identified high impact packages from our Pilot Program List |
I'm no longer abreast of where our tooling is, but if there's a one-liner command i can run to make all the changes required in a git working directory, I can start doing it in my 350 packages. Do we have that yet? |
@ljharb This is the tooling we have - https://github.com/pkgjs/support. Let us know if you have questions/that does not do what you are looking for. |
The tool includes "best-effort", but https://github.com/nodejs/package-maintenance/blob/HEAD/docs/PACKAGE-SUPPORT.md does not - did we remove that since it's basically the same as "time-permitting"? |
I've added support info to v1.20.2 of https://npmjs.com/object-inspect. |
@ljharb what version are you using? This commit - pkgjs/support@597303a removed best-effort If you are using 0.0.5 that means I should publish a new version. |
I'm using whatever's latest; that commit is indeed unreleased. |
@ljharb published a new version of the support package. |
I'm going to close this in favor of trying to find some more specific actions/issues. |
Add the suggestions. volunteer here
The text was updated successfully, but these errors were encountered: