Node.js Foundation Modules Team Meeting 2018-09-12 #179
Comments
|
@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
|
|
Are many of the questions like that one, where they ask a question about an implementation detail and not about use cases and defaults? |
|
@SMotaal I've updated the agenda accordingly. Please lmk if this does not accurately reflect your request |
|
@ljharb please complete the survey, and let's discuss your feedback in the meeting, which works much better if you actually take the survey 👍 |
|
@SMotaal sure, where's the link for it? |
|
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. |
|
@MylesBorins can we also address having an internal mailing list in pre/post. I wish forms worked with GitHub logins, they don't yet. |
|
@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) |
|
While GitHub and Google folks land this... let's just use this form to collect emails/usernames: https://goo.gl/forms/DVsmE9HWXQKBNO0J3 🎉 |
|
I think we can remove the |
|
I was thinking this creates a spreadsheet that links the two, sounds good? |
|
@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. |
|
Here is an open link to the most recent "ongoing" draft: C1: Developers Survey |
Time
UTC Wed 12-Sep-2018 19:00 (07:00 PM):
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 (2 minute timebox)
Update on Progress (6 minute timebox)
Discussion (40 minute timebox)
Thinking about deadlines #123
Survey: Initial Draft #173
Managing fork and agreed upon minimal kernel #166
Invited
Notes
The agenda comes from issues labelled with
modules-agendaacross 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
The text was updated successfully, but these errors were encountered: