Skip to content

Latest commit

 

History

History
85 lines (60 loc) · 3.41 KB

2020-05-05.md

File metadata and controls

85 lines (60 loc) · 3.41 KB
Raw

Node.js Package Maintenance Team Meeting 2020-05-05

Links

Present

  • Glenn Hinks @ghinks
  • Lucas Holmquist @lholmquist
  • Michael Dawson (@mhdawson)
  • Wes Todd (@wesleytodd)
  • Dominykas Blyžė (@dominykas)
  • Package Maintenance team: @nodejs/package-maintenance
  • Andrew Hughes (@andrewhughes101)
  • Owen Buckley (@thescientist13)
  • Jordan Harband (@ljharb)
  • Tierney Cyren
  • Rick Markins (@rxmarbles)

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

  • Submit sessions to Collab Summit #335

    • Wes, what is the format
    • Michael gave short, possibly inaccurate description
    • Glenn, we should have quite a lot to talk about
    • Wes, part of reason we got engagement was because it was in person will be interested to see if we get the same out of a virtual event.
    • Michael, could make sense to focus on aspects that benefit from broader audience
    • Glen, possibly talk with some of the other open JS projects, are other maintainers interested.
    • Owen, since Axios was mentioned, one of the key factors was identifying champions maintainer
    • Wes will volunteer to open issue for session and team members know when its there for comment.

  • Dependents tooling #327

    • Issue has been created to request repo
      nodejs#352
    • suggested name is "will-I-break-you" or wiby
    • No objections from those in attendance.

  • PkgJS Org for WG supported tooling #271

    • discussion on proposed governance - nodejs#338

    • Tierney, has org management tool for electron. Bot deployed to heroku that configures and manages repo creation, integrates with slack, identifies if things that are wrong (for example member access level changed manually instead of through tool)

    • Wes, questions

      • Does this matter for the charter ?
      • npm publish management would be another desired feature
      • who would run the instance?

    • Wes what about npm publish,

      • Tierney they might accept a plug in but will likely not do it themselves

    • Some discussion on the charter.

  • Next steps on Support levels in Package.json #192

  • Michael point out nodejs#355 for those who might be interested

Project Board Review (maybe, if time permits).

Ask participants about the state of Project Board and necessary changes if time permits.

Q&A, Other

@ghinks would like to share the current progress with the express JS triage team. We will be coming up to the next collaborators conference soon and progress has been made.

Upcoming Meetings

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