Node.js Package Maintenance Team Meeting 2021-07-29

[mhdawson]

Time

UTC Thu 29-Jul-2021 17:00 (05:00 PM):

Timezone	Date/Time
US / Pacific	Thu 29-Jul-2021 10:00 (10:00 AM)
US / Mountain	Thu 29-Jul-2021 11:00 (11:00 AM)
US / Central	Thu 29-Jul-2021 12:00 (12:00 PM)
US / Eastern	Thu 29-Jul-2021 13:00 (01:00 PM)
EU / Western	Thu 29-Jul-2021 18:00 (06:00 PM)
EU / Central	Thu 29-Jul-2021 19:00 (07:00 PM)
EU / Eastern	Thu 29-Jul-2021 20:00 (08:00 PM)
Moscow	Thu 29-Jul-2021 20:00 (08:00 PM)
Chennai	Thu 29-Jul-2021 22:30 (10:30 PM)
Hangzhou	Fri 30-Jul-2021 01:00 (01:00 AM)
Tokyo	Fri 30-Jul-2021 02:00 (02:00 AM)
Sydney	Fri 30-Jul-2021 03:00 (03:00 AM)

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Package%20Maintenance%20Team+Meeting+2021-07-29&iso=20210729T1700
• or https://www.wolframalpha.com/input/?i=05PM+UTC%2C+Jul+29%2C+2021+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1sGDxvhqX58ABNJ68TQOUzdM4PYz4mjF4_Rnwkch2c7s/edit

Agenda

Extracted from package-maintenance-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/package-maintenance

• Status update and next steps for "pkgjs/create" (create-pkg) #458
• Suggested list of modules to help get support info into #413

Invited

• Package Maintenance team: @nodejs/package-maintenance

Observers/Guests

Notes

The agenda comes from issues labelled with package-maintenance-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

• link for participants: https://zoom.us/j/431077278
• For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live
• youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

[thescientist13]

Just wanted to highlight @jonchurch has been grooming the issue tracker and has helped surface some good (IMO) topics that could be useful to review with the group here.
https://github.com/nodejs/package-maintenance/issues?q=is%3Aopen+is%3Aissue+label%3Astale%3F

As it looks like the agenda is pretty light today maybe we could brush the dust off some of the above items? In particular these seem pretty compelling / interesting (to me anyway) and others may just simply be stale and just need to be closed.

1. Suggestion: definition of "at risk" packages using heuristics #97
2. Suggestion: maintainers guidance and platform/forum for finding new maintainers #4 (-> [tool] used-by -- find the biggest users of a package #214)

Will leave it up to the team to see if anything catches anyone eye in the above filter. 🔍 👀

[jonchurch]

Hey all, I have created a new (hopefully temporary) label called stale? which I'm marking some issues with. I don't like the idea of stale'ing issues, but let me explain my goal.

There's a lot of great discussions and ideas that have happened in this repo. Some we have outgrown, or are out of scope for where we are currently. Instead of closing a lot of issues, I'd like to organize some issues that could be closed, but I want others to take a look at and see if they want to close them, or find them to be relevant now and want to breathe life into them.

See issues that have been recently closed to check my closing work.

I also found an old idea for a tool #214 that was hidden away, would be cool to look at again!

Hahha @thescientist13 tyty, we are both commenting at the same time I see.

Edit: I just tossed an agenda label on #373 (Draft documentation promotion) just so we can keep an eye on it for our next meeting.

[mhdawson]

PR for minutes: #475