This repository has been archived by the owner on Jan 10, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 18
Node.js End User Feedback (NEUF) Meeting 2017-12-01 #6
Labels
Comments
Doodle for this meeting: https://doodle.com/poll/96r9czpw6x9ds7zg Please note your availability. Please raise your hand if you'd like to participate. |
Unfortunately I will be onsite with clients (in St Louis) the week after Thanksgiving. |
Add "#7, Update README To add my email address" to agenda. Let's celebrate our first small win with the first landed PR. |
Add #8, Supporting the Node.js 2018 User Survey. |
Add nodejs/community-committee#153, Benchmarking team request for survey. Questions are ready for outreach. |
dshaw
changed the title
Node.js End User Feedback (NEUF) Meeting 2017-11-XX
Node.js End User Feedback (NEUF) Meeting 2017-12-01
Nov 30, 2017
@mhdawson Can you help get this setup as a Google Hangout On Air on the Node.js Account today? |
Sorry did not see this. Will set it up now |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Node.js End User Feedback (NEUF) Meeting 2017-12-01
Time
Friday, 2017-12-01 at 17:00 UTC / noon ET / 11am CT / 9am PT
Links
Agenda
Extracted from neuf-agenda labelled issues and pull requests from the user-feedback repo prior to the meeting.
Invited
Public participation
The Node.js project live streams meetings so anyone can tune in. Everyone is invited to participate in the live chat. The stream will start playing at https://www.youtube.com/c/nodejs+foundation/live once we go live.
There's usually a short cat-herding time at the start of the meeting and occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and we'll be online shortly. ❤️
Joining the meeting
Join link for invited members and observers: https://zoom.us/j/346639155
There is a standing invitation for all @nodejs/TSC and @nodejs/community-committee members to attend in observer capacity.
The text was updated successfully, but these errors were encountered: