Skip to content

Commit c1f1117

Browse files
authored
doc: add minutes for meeting 20 June 2023 (#565)
Signed-off-by: Michael Dawson <mdawson@devrus.com>
1 parent 487f949 commit c1f1117

1 file changed

Lines changed: 54 additions & 0 deletions

File tree

meetings/2023-06-20.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# Node.js Package Maintenance Team Meeting 2023-06-20
2+
3+
## Links
4+
5+
* **Recording**: <https://www.youtube.com/watch?v=Lz4C_WtCzeo>
6+
* **GitHub Issue**: <https://github.com/nodejs/package-maintenance/issues/564>
7+
8+
## Present
9+
10+
* Michael Dawson (@mhdawson)
11+
* Wes Todd (@wesleytodd)
12+
* Owen Buckley (@thescientist13)
13+
* Ruy Adorno (@ruyadorno)
14+
15+
## Agenda
16+
17+
## Announcements
18+
19+
*Extracted from **package-maintenance-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting.
20+
21+
* Wes, netflix is hiring Node.js people.
22+
23+
### nodejs/package-maintenance
24+
25+
* Goals for 2023 [#550](https://github.com/nodejs/package-maintenance/issues/550)
26+
* two items cover package.json
27+
* ecosystem keys and best practices
28+
* seems quite similar to documenting runtime support
29+
* <https://github.com/openjs-foundation/cross-project-council/issues/1102>
30+
* Michael - this looks related - <https://github.com/openjs-foundation/cross-project-council/issues/1102>
31+
* Michael - also channel with related discussion - <https://openjs-foundation.slack.com/archives/C05AWQH5E4R> (improve-package-json)
32+
* Wes agreed, just figuring out what we want to do. Idea is to find documentation for existing keys/set of keys that are already being used
33+
* For example, we configure out the common subset between npm, yarn, pnpm, etc.
34+
* Could be use as jumping off point to get alignment across similar usage (runtime, package manager etc.)
35+
* Also good ways to better understand what Package.json depends on, for example SemVer
36+
* Michael sounds like the ongoing effort is something that Package-maintenance team should participate but not its’ being driven at on a more general non node.js specific level.
37+
38+
* Create doc on how to support ESM and CommonJS when publishing modules [#542](https://github.com/nodejs/package-maintenance/issues/542)
39+
* No update this week
40+
41+
* Status update and next steps for "pkgjs/create" (create-pkg) [#458](https://github.com/nodejs/package-maintenance/issues/458)
42+
* Discussed and suggested that Ethan connect with Wes to define the plan/next steps.
43+
44+
## Project Board Review (maybe, if time permits)
45+
46+
Ask participants about the state of [Project Board](https://github.com/nodejs/package-maintenance/projects/1) and necessary changes if time permits.
47+
48+
## Q&A, Other
49+
50+
## Upcoming Meetings
51+
52+
* **Node.js Project Calendar**: <https://nodejs.org/calendar>
53+
54+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

0 commit comments

Comments
 (0)