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

[mhdawson]

Time

UTC Tue 29-Jun-2021 19:00 (07:00 PM):

Timezone	Date/Time
US / Pacific	Tue 29-Jun-2021 12:00 (12:00 PM)
US / Mountain	Tue 29-Jun-2021 13:00 (01:00 PM)
US / Central	Tue 29-Jun-2021 14:00 (02:00 PM)
US / Eastern	Tue 29-Jun-2021 15:00 (03:00 PM)
EU / Western	Tue 29-Jun-2021 20:00 (08:00 PM)
EU / Central	Tue 29-Jun-2021 21:00 (09:00 PM)
EU / Eastern	Tue 29-Jun-2021 22:00 (10:00 PM)
Moscow	Tue 29-Jun-2021 22:00 (10:00 PM)
Chennai	Wed 30-Jun-2021 00:30 (12:30 AM)
Hangzhou	Wed 30-Jun-2021 03:00 (03:00 AM)
Tokyo	Wed 30-Jun-2021 04:00 (04:00 AM)
Sydney	Wed 30-Jun-2021 05:00 (05:00 AM)

Or in your local time:

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

Links

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

Agenda

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

nodejs/package-maintenance

• Let's fork actions/setup-node? #462
• 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

[mhdawson]

PR for minutes: #471

[jonchurch]

Follow up from the meeting re: pkgjs/create status, copied from my comment at #458

Caught up with wes today about this briefly. He hasn't had the time to keep up with current discussions in the repo so things haven't progressed.

In order to move forward it needs:

• People who understand the problem the project intends to address and can communicate it in simple terms (aka likely create some tickets to be worked on)
• Someone(s) who have the time and desire to work on it, make decisions, and push code
• Edit: Giving commit bits to contributors

I brought up finding some funding for the project to help someone(s) be able to dedicate time to it. Good candidates would be companies who have an interest in solving problems in the scaffolding landscape, most notably NPM could benefit from this project.

So classic issues of momentum and human hours being needed to kickstart the project, which could be addressed by someone taking charge and funding being provided. For those who would like to get involved, this existing issue lays out the motivation and imagined project structure.