You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 2, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 2, 2023. It is now read-only.
Node.js Foundation Modules Team Meeting 2018-09-12 #179
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.
@MylesBorins Several team members have been working really hard on a two-track survey effort (developers and internal) for the Modules WG. Today, we are sending out invites to @zenparsing's B1 (internal track) version and hope to get at least 10 responses till then. Both @sendilkumarn and @devsnek are coordinating to ensure we include everyone in the WG, until we figure out a more structured mechanism to avoid missing or outdated recipients.
At the same time, the rest of us folks in #175 are hashing out final edits to C1 (developers track) which is the first draft resulting from multiple iterations that will be open to WG members, and will start the en masse review process, as soon as everyone indicates in B1 which aspects of the survey they are interested/positioned to improve on.
We are going to need time for (if possible):
(10 min) Talk about B1 (internal track)
(5 min) Talk about C1 (developers track)
I've been very distracted lately ("again" not my best year I guess) but thanks to everyone else involved, this effort which was stalled is now well on it's way to bring the much needed inputs needed by the WG.
I mention this here because there is no dedicated issue (avoiding noise with related 3 issues already).
@MylesBorins The last question in the survey can help us start matching people with shared interests together:
For each aspect, the people who will work together will select a point person that drives consensus within as they coordinate with the rest other groups when there is overlap.
We'll wait for 24 hours to give a chance for those who are still planning to fill out B1 to do so then create a new issue with links to the C1 draft and a listing of those interested for each aspect.
Activity
SMotaal commentedon Sep 12, 2018
@MylesBorins Several team members have been working really hard on a two-track survey effort (developers and internal) for the Modules WG. Today, we are sending out invites to @zenparsing's B1 (internal track) version and hope to get at least 10 responses till then. Both @sendilkumarn and @devsnek are coordinating to ensure we include everyone in the WG, until we figure out a more structured mechanism to avoid missing or outdated recipients.
At the same time, the rest of us folks in #175 are hashing out final edits to C1 (developers track) which is the first draft resulting from multiple iterations that will be open to WG members, and will start the en masse review process, as soon as everyone indicates in B1 which aspects of the survey they are interested/positioned to improve on.
We are going to need time for (if possible):
I've been very distracted lately ("again" not my best year I guess) but thanks to everyone else involved, this effort which was stalled is now well on it's way to bring the much needed inputs needed by the WG.
I mention this here because there is no dedicated issue (avoiding noise with related 3 issues already).
TEASER
ljharb commentedon Sep 12, 2018
Are many of the questions like that one, where they ask a question about an implementation detail and not about use cases and defaults?
MylesBorins commentedon Sep 12, 2018
@SMotaal I've updated the agenda accordingly. Please lmk if this does not accurately reflect your request
SMotaal commentedon Sep 12, 2018
@ljharb please complete the survey, and let's discuss your feedback in the meeting, which works much better if you actually take the survey 👍
ljharb commentedon Sep 12, 2018
@SMotaal sure, where's the link for it?
SMotaal commentedon Sep 12, 2018
We have to email invites and we're still working with everyone on the team to ensure we have your emails. Can you please email me to include you.
SMotaal commentedon Sep 12, 2018
@MylesBorins can we also address having an internal mailing list in pre/post. I wish forms worked with GitHub logins, they don't yet.
sendilkumarn commentedon Sep 12, 2018
@MylesBorins yeah having that list will be very handy for sending out these communications and looking for faster feedbacks.
@SMotaal Is there some other forms that work with Github logins? (It seems like an interesting idea)
SMotaal commentedon Sep 12, 2018
While GitHub and Google folks land this... let's just use this form to collect emails/usernames: https://goo.gl/forms/DVsmE9HWXQKBNO0J3
🎉
sendilkumarn commentedon Sep 12, 2018
I think we can remove the
githubusername there?SMotaal commentedon Sep 12, 2018
I was thinking this creates a spreadsheet that links the two, sounds good?
SMotaal commentedon Sep 12, 2018
@MylesBorins The last question in the survey can help us start matching people with shared interests together:
For each aspect, the people who will work together will select a point person that drives consensus within as they coordinate with the rest other groups when there is overlap.
SMotaal commentedon Sep 12, 2018
We'll wait for 24 hours to give a chance for those who are still planning to fill out B1 to do so then create a new issue with links to the C1 draft and a listing of those interested for each aspect.
SMotaal commentedon Sep 12, 2018
Here is an open link to the most recent "ongoing" draft: C1: Developers Survey