Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add minutes for meeting 13 May 2019 #213

merged 2 commits into from May 17, 2019
Changes from 1 commit
File filter...
Filter file types
Jump to…
Jump to file or symbol
Failed to load files and symbols.


Just for now

@@ -0,0 +1,70 @@
# Node.js Foundation Package Maintenance Team Meeting 2019-05-06

## Links

* **Recording**:
* **GitHub Issue**:

## Present

* Michael Dawson (@mhdawson)
* Rick Markins (@rxmarbles)
* Dominykas Blyžė (@dominykas)
* Joel Chen (@jchip)
* Edgar Muentes (@emuentes)
* Glen Hinks (@ghinks)
* Manuel Spigolon (@eomm)
This conversation was marked as resolved by mhdawson

This comment has been minimized.

Copy link

ljharb May 15, 2019

Suggested change
* Manuel Spigolon (@eomm)
* Manuel Spigolon (@eomm)
* Jordan Harband (@ljharb)

## Agenda

## Announcements

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

* Some discussion around who will be at the collab summit. Sounds like we should
Have 5 or 6 people plus hopefully others we can get interested in joining the conversations.

### nodejs/package-maintenance

* \[key packages\] A list of packages that do not test in latest LTS [#200](
* Good discussion on issue. Created issues #204, #205, #206 and #207 to
push forward.

* Session at Node.js collaborator summit [#189](
* Session submitted, will leave open until summit occurs.

* \[baseline practices\] .npmignore or package.json files [#164](
* good discussion, going to split out bigger picture into

* RFC: Proposal for configurable way to npm install only the desired files from npm modules
*Document the “paved paths”
* Propose a process for packages maintainers to indicate explicitly which
files are needed for production (possibly through globs)
* Make a tool for maintainers to get feedback and suggestions to drive dev decisions
that support the ability for consumers to choose how much to install
* add deprecate guidelines doc \[draft\] [#150](
* Defer to next time as we ran out of time
* Which Problems Node.js OSS maintainers/authors face today? [#113](
* Defer to next time as we ran out of time
* Next steps on Support levels in Package.json
* Defer to next time as we ran out of time
## Project Board Review (maybe, if time permits).
Ask participants about the state of [Project Board]( and necessary changes if time permits.
## Q&A, Other
## Upcoming Meetings
* **Node.js Foundation Calendar**:

Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

ProTip! Use n and p to navigate between commits in a pull request.
You can’t perform that action at this time.