Skip to content

Node.js Foundation Package Maintenance Team Meeting 2019-09-24 #259

Closed

Description

@mhdawson

Time

UTC Tue 24-Sep-2019 19:00 (07:00 PM):

Timezone Date/Time
US / Pacific Tue 24-Sep-2019 12:00 (12:00 PM)
US / Mountain Tue 24-Sep-2019 13:00 (01:00 PM)
US / Central Tue 24-Sep-2019 14:00 (02:00 PM)
US / Eastern Tue 24-Sep-2019 15:00 (03:00 PM)
London Tue 24-Sep-2019 20:00 (08:00 PM)
Amsterdam Tue 24-Sep-2019 21:00 (09:00 PM)
Moscow Tue 24-Sep-2019 22:00 (10:00 PM)
Chennai Wed 25-Sep-2019 00:30 (12:30 AM)
Hangzhou Wed 25-Sep-2019 03:00 (03:00 AM)
Tokyo Wed 25-Sep-2019 04:00 (04:00 AM)
Sydney Wed 25-Sep-2019 05:00 (05:00 AM)

Or in your local time:

Links

Agenda

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

nodejs/package-maintenance

  • Future direction support field #241
  • Standard grammar/keywords to reference node release lines #236
  • Document the current 'top 10' express' issues #233
  • Next steps on Support levels in Package.json #192
  • [baseline practices] .npmignore or package.json files #164
  • Which Problems Node.js OSS maintainers/authors face today? #113

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


Invitees

Please use the following emoji reactions in this post to indicate your
availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure yet

Activity

  1. self-assigned this
    on Sep 18, 2019
  2. Trott commented on Sep 18, 2019

    @Trott
    Member

    Not sure if this fits in with the package-maintenance team's goals/charter/whatever, but assistance getting things aligned in the ecosystem and Node.js 13.0.0 such that we minimize the pain of any Node.js breaking changes for end users would be 💯. Specifically, it would be great if we could get rid of as many CITGM issues there as possible.

  3. wesleytodd commented on Sep 18, 2019

    @wesleytodd
    Member

    @Trott Making this easier for maintainers in general is within this groups charter (even if specific upgrades might not be something we are equipped to handle yet). Are there specific things you think we could help with? Also, this might warrant a separate issue so we can discuss and then add to this meeting agenda if there is more to talk about.

  4. Trott commented on Sep 18, 2019

    @Trott
    Member

    Are there specific things you think we could help with?

    I had contributing fixes in mind, but if that's not in scope, then maybe nothing much comes to mind. Perhaps just getting the word out to folks who might contribute fixes, but that can be some effort. Perhaps coordinating with @nodejs/mentorship to see if maybe this is something mentors/mentees can look at? Or @nodejs/code-and-learn?

  5. dominykas commented on Sep 23, 2019

    @dominykas
    Member

    Added #244 to agenda, because its something I intend to look deeper into over the next month or so.

  6. lholmquist commented on Sep 24, 2019

    @lholmquist
    Contributor

    looks like i'm going to miss this one, i'll catch up on the recording 👎

  7. craftninja commented on Sep 24, 2019

    @craftninja
    Contributor

    @mhdawson FWIW - I love the emoji respond section for attendance! I just noticed it now...

    I will be missing this one but will catch up later today.

  8. mhdawson commented on Sep 24, 2019

    @mhdawson
    MemberAuthor

    PR for minutes: #262

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions