doc: add minutes for meeting 8 Sep 2020

meetings/2020-09-08.md

@@ -0,0 +1,83 @@
+# Node.js  Package Maintenance Team Meeting 2020-09-08
+
+## Links
+
+* **Recording**: https://youtu.be/F5iYERQrDX0
+* **GitHub Issue**: https://github.com/nodejs/package-maintenance/issues/405
+
+## Present
+
+* Package Maintenance team: @nodejs/package-maintenance
+
+* Wes Todd (@wesleytodd)
+* Michael Dawson (@mhdawson)
+* Darcy Clarke (@darcyclarke)
+* Dominykas Blyžė (@dominykas)
+* Glenn HInks (@ghinks)
+* Bethany Griggs
+* Ash Cripps (@AshCripps)
+* Owen Buckley (@thescientist13)
+
+## Agenda
+
+## Announcements
+
+*Extracted from **package-maintenance-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
+
+* No announcements this week.
+
+### nodejs/package-maintenance
+
+* Building `create-pkg` [#404](https://github.com/nodejs/package-maintenance/issues/404)
+  * create-pkg ownership transferred to the @pkgjs org on npmjs.com.
+  * npm uses create-x as identifier as template. Therefore npm init pkg runs that package.
+  * we can use to create some good defaults
+  * repo https://github.com/pkgjs/create will be used to build this out.
+    * had been used to scaffold out an earlier version
+    * need to delete/move code somewhere else and then use this repo to build out the package as
+      outlined in the issue.
+  * the list shown is a superset of the defaults used by current npm default init
+  * Next steps:
+    * out of band call on technical structure etc. Wes will set up through issue after call.
+    * get some general consensus of the approach we'd like to take building this & the
+       defaults we'd want
+    * update @pkgjs/support to be a consumer of this tool or vice-versa
+
+* docs: PR landing, with outstanding reviews 
+[#403](https://github.com/nodejs/package-maintenance/pull/403)
+  * no objections, will wait until we hit the 14 days and then land unless there are objections.
+
+* Adding Package Maintenance to NodeJS website [#402](https://github.com/nodejs/package-maintenance/issues/402)
+  * discussed briefly, no objections to what has been suggested in the issue.
+
+* nodejs/package-compliant vs @pkgjs/support [#401](https://github.com/nodejs/package-maintenance/issues/401)
+  * need to do release of support, point to 
+  * we should archive package-compliant, then do final publish to indicate deprecated.
+
+* Draft text for support info blog post [#399](https://github.com/nodejs/package-maintenance/issues/399)
+  * Agreement in the meeting we can move to publishing step.
+
+* Communicating that only the latest version of a major release line is supported [#393](https://github.com/nodejs/package-maintenance/issues/393)
+  * Some updates to the readme, please review/approve
+
+* Suggest ignoring a vulnerability by the package maintainer [#386](https://github.com/nodejs/package-maintenance/issues/386)
+  * lets schedule a separate deep dive to talk about this one (Michael took action)
+
+* PkgJS Org for WG supported tooling [#271](https://github.com/nodejs/package-maintenance/issues/271)
+  * very close to being ready to integrate into Node.js project teams (moderation, etc.)
+
+* Next steps on Support levels in Package.json [#192](https://github.com/nodejs/package-maintenance/issues/192)
+  * talked about blog post, above
+  * other tasks on the issue. 
+
+## Project Board Review (maybe, if time permits).
+
+Ask participants about the state of [Project Board](https://github.com/nodejs/package-maintenance/projects/1) and necessary changes if time permits.
+
+## Q&A, Other
+
+## Upcoming Meetings
+
+* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.