You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Suggested list of modules to help get support info into #413
Curious @mhdawson what, if any, remaining action items are left on this? If there are some, a quick summary status may be helpful for those coming into this issue and how contributions to help complete it may be supported, if applicable.
@thescientist13 we still need to figure out how to get more packages/modules to adopt. Having said that, this issue being on the agenda is not helping to move that forward so I'd be ok with closing it until I have more time to define some more concrete next steps.
Ah, so just a "socialization" effort? I think if that's the case, leaving it on the agenda is fine, maybe just supplemented with a CTA for members to spread the word then? Or something worth sharing via Slack channels? Or another method not already tried yet?
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?
Activity
boneskull commentedon Oct 15, 2020
@mhdawson Can you please provide some more context here? What am I volunteering for? 😄
mhdawson commentedon Oct 19, 2020
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.
mhdawson commentedon Oct 20, 2020
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.
mhdawson commentedon Nov 24, 2020
PR to add support info in node-addon-api -> nodejs/node-addon-api#843
mhdawson commentedon Jan 12, 2021
The PR to add to node-addon-api landed.
Its been added to the modules in github/nodeshift.
shadowspawn commentedon Mar 26, 2021
Support info has been added to https://github.com/tj/commander.js
mhdawson commentedon Mar 26, 2021
@shadowspawn thanks !
thescientist13 commentedon Sep 30, 2021
Curious @mhdawson what, if any, remaining action items are left on this? If there are some, a quick summary status may be helpful for those coming into this issue and how contributions to help complete it may be supported, if applicable.
mhdawson commentedon Oct 1, 2021
@thescientist13 we still need to figure out how to get more packages/modules to adopt. Having said that, this issue being on the agenda is not helping to move that forward so I'd be ok with closing it until I have more time to define some more concrete next steps.
thescientist13 commentedon Oct 4, 2021
Ah, so just a "socialization" effort? I think if that's the case, leaving it on the agenda is fine, maybe just supplemented with a CTA for members to spread the word then? Or something worth sharing via Slack channels? Or another method not already tried yet?
thescientist13 commentedon May 12, 2022
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
ljharb commentedon May 12, 2022
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?
mhdawson commentedon May 24, 2022
@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.
ljharb commentedon May 26, 2022
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"?
ljharb commentedon May 26, 2022
I've added support info to v1.20.2 of https://npmjs.com/object-inspect.
mhdawson commentedon May 27, 2022
@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.
ljharb commentedon May 28, 2022
I'm using whatever's latest; that commit is indeed unreleased.
mhdawson commentedon Jun 21, 2022
@ljharb published a new version of the support package.
mhdawson commentedon Dec 22, 2022
I'm going to close this in favor of trying to find some more specific actions/issues.