Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

Node.js Foundation Modules Team Meeting 2018-11-07 #217

Closed
MylesBorins opened this issue Nov 6, 2018 · 16 comments
Closed

Node.js Foundation Modules Team Meeting 2018-11-07 #217

MylesBorins opened this issue Nov 6, 2018 · 16 comments

Comments

@MylesBorins
Copy link
Contributor

MylesBorins commented Nov 6, 2018

Time

UTC Wed 07-Nov-2018 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Wed 07-Nov-2018 12:00 (12:00 PM)
US / Mountain Wed 07-Nov-2018 13:00 (01:00 PM)
US / Central Wed 07-Nov-2018 14:00 (02:00 PM)
US / Eastern Wed 07-Nov-2018 15:00 (03:00 PM)
London Wed 07-Nov-2018 20:00 (08:00 PM)
Amsterdam Wed 07-Nov-2018 21:00 (09:00 PM)
Moscow Wed 07-Nov-2018 23:00 (11:00 PM)
Chennai Thu 08-Nov-2018 01:30 (01:30 AM)
Hangzhou Thu 08-Nov-2018 04:00 (04:00 AM)
Tokyo Thu 08-Nov-2018 05:00 (05:00 AM)
Sydney Thu 08-Nov-2018 07:00 (07:00 AM)

Or in your local time:

Links

Agenda

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

Approving PRs (13 minute timebox)

  • Add @ryzokuken as Observer #213
    • 1 minute timbox
  • @bmacnaughton requesting membership/observer #211
    • 1 minute timbox
  • governance: be explicit about meetings new members can join #218
    • 1 minute timebox
  • esm: refactor dynamic modules #9
    • 5 minute timebox
  • Add format distinction to phase 2 #215
    • 5 minute timebox

Update on Progress (1 minute timebox)

  • Surveys: Members formally taking ownership (leadership) is the next step #209
    • 1 minute timebox

Discussion (40 Minute Timebox)

Invited

  • Modules team: @nodejs/modules

Notes

The agenda comes from issues labelled with modules-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

@MylesBorins
Copy link
Contributor Author

I will not be around tomorrow unfortunately, will anyone else be able to chair / get the stream going?

Is agenda looking good? anything missing?

@SMotaal
Copy link

SMotaal commented Nov 7, 2018

I just went through and removed the modules-agenda label from some issues to make time for the more pressing Phase 2 discussions.

Here is what I deferred: #184, #173, #182

Only #209 needs to be mentioned, not really a discussion, just to try to bring to the attention of the group that the next steps fall on everyone involved and my personal view on the future implications of a successful survey.

@guybedford
Copy link
Contributor

@SMotaal I've updated the agenda to reflect this. Did you still want to discuss #169 as well?

@guybedford
Copy link
Contributor

I've tentatively added an agenda item for the explicit package exports proposal, but we will have to see how the timing works out if we can fit this in.

@SMotaal
Copy link

SMotaal commented Nov 7, 2018

@guybedford Let's defer #209 and #169 to next meeting to free up needed time as per emails.

Specific to #209, I think the actual discussion can move to next meeting, but can you please bring it to attention of the group so that everyone would take the time to read it afterwards, act, discuss or ignore as they see fit.

@MylesBorins sorry just caught your comment above 😊

@SMotaal
Copy link

SMotaal commented Nov 7, 2018

@inidaname: you added modules-agenda to #85 back in May21… is it safe to assume it is not relevant for this meeting?

If so, can we also remove the label until it is needed?

@SMotaal SMotaal mentioned this issue Nov 7, 2018
@MylesBorins
Copy link
Contributor Author

I've updated the agenda to reflect the above conversation. I've left #209 on the agenda as a 1 minute item for a very quick update. Explicit package exports proposal has a 5 minute timebox at the end of the meeting, but we will be able to spend more time on it if we wrap up other items faster

@GeoffreyBooth
Copy link
Member

Within the discussion timebox, could we discuss the items related to Phase 2 first? To try to keep momentum going. If we run out of time I'd rather lose the non-Phase 2 topics.

@devsnek
Copy link
Member

devsnek commented Nov 7, 2018

we can't actually do any code until the repo is updated. 197 should be a top priority.

@MylesBorins
Copy link
Contributor Author

@devsnek do you have a proposal for how we should manage the fork to keep it up to date?

@devsnek
Copy link
Member

devsnek commented Nov 7, 2018

@MylesBorins someone needs to rebase it. same process that happens in nodejs/node-v8 and nodejs/node#canary-base

@jdalton
Copy link
Member

jdalton commented Nov 7, 2018

I'll likely miss this one but I reviewed, approved, updooted the approving PR section items.

@MylesBorins
Copy link
Contributor Author

I've added #218 as a 1 minute timebox item

@MylesBorins
Copy link
Contributor Author

For some reason zoom is refusing to load for me right now, apologies for delay

@giltayar
Copy link

giltayar commented Nov 7, 2018

I can't connect for some reason.

@SMotaal
Copy link

SMotaal commented Nov 7, 2018

Zoom needs a 5 second bleep button and maybe in our case a 5 minute one is more useful 😅

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants