Skip to content
This repository has been archived by the owner on Jan 10, 2020. It is now read-only.

2017-12-15 Node.js End User Feedback (NEUF) Meeting #17

Closed
dshaw opened this issue Dec 1, 2017 · 14 comments
Closed

2017-12-15 Node.js End User Feedback (NEUF) Meeting #17

dshaw opened this issue Dec 1, 2017 · 14 comments
Assignees

Comments

@dshaw
Copy link
Contributor

dshaw commented Dec 1, 2017

2017-12-15 Node.js End User Feedback (NEUF) Meeting

Time

Friday, 2017-12-15 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/547639541

There is a standing invitation for all @nodejs/TSC and @nodejs/community-committee members to attend in observer capacity.

@dshaw
Copy link
Contributor Author

dshaw commented Dec 14, 2017

Inviting @jasnell @ahmadnassri and @tlivings for #18

@mikehostetler
Copy link
Contributor

Unfortunately I will not be able to attend this one. Looking forward to reviewing the notes!

@ZibbyKeaton
Copy link

I will also not be able to attend this meeting. I will listen to the recording and follow up with Greg too on next steps and support needed from NF.

@bnb
Copy link
Contributor

bnb commented Dec 14, 2017

Seeing as this meeting hasn't happened yet, I'd like to request that the cc-agenda label not be added. Would be a good thing for @mhdawson to bring up in his report to the CommComm, though! 👍

@bnb bnb removed the cc-agenda label Dec 14, 2017
@williamkapke
Copy link

I'm also not able to attend this one. (dentist appt)

@mhdawson
Copy link
Member

I won't be able to make it as I'm on holiday starting Friday.

@dshaw
Copy link
Contributor Author

dshaw commented Dec 14, 2017

@bnb I'm not sure I understand your feedback. I added the cc-agenda label because this meeting was happening after the CommComm meeting. I thought the NEUF meeting topics this week would be of interest to other members of the CommComm and wanted to invite folks from the CommComm to participate. So is your feedback that this is something you do not want to see in CommComm meetings in the future as a proposed agenda item?

Also worth noting, I am the individual leading this initiative. I asked @mhdawson to be our "Champion" because none of the core organizing group were full CommComm members when this initiative was bootstrapped. I thought we would need help getting things setup and someone to sanity check undocumented expectations and processes or even just to find documented ones. (We very much did and still do.) If there are any questions about this initiative, please direct them to me Please reach out to @mhdawson if we ever go off the rails on CommComm processes so he can help us improve or get back in line.

@DiegoZoracKy
Copy link

Hi @dshaw, can I join this meeting as an Observer? It seems to me that what will be discussed here regarding NEUF can be in some way related to what we talked about, on yesterday's meeting.

@bnb
Copy link
Contributor

bnb commented Dec 15, 2017

@dshaw for context: the cc-agenda label is added for issues with things to be discussed that need extra attention/need explicit action from the CommComm meeting.

Since we have the report on initiatives at the beginning of the meeting, that's a fantastic time to request members to come to a meeting being held in the future (i.e. something with no present action/decision to be made) - and likely doesn't need to be Community Committee agenda item, but rather can be a normal part of the reporting process 👍

@ghost
Copy link

ghost commented Dec 15, 2017

Hi,
can somebody fix the links from Governance and Contributing area from Readme file?
I think they should direct to https://github.com/nodejs/community-committee/blob/master/GOVERNANCE.md and https://github.com/nodejs/community-committee/blob/master/CONTRIBUTING.md . Thank you.

@dshaw
Copy link
Contributor Author

dshaw commented Dec 15, 2017

Thank you, @bnb for setting up the Zoom meeting.
https://zoom.us/j/547639541

Note that this is a change from what was on the calendar up until today. (Each Zoom Meeting is unique. So we can’t publish these links until the day of the meeting. 😕

@dshaw
Copy link
Contributor Author

dshaw commented Dec 15, 2017

@DiegoZoracKy Please join us. Sounds good.

@bnb
Copy link
Contributor

bnb commented Dec 15, 2017

Benchmarking survey request issue: nodejs/community-committee#153

@dshaw
Copy link
Contributor Author

dshaw commented Dec 15, 2017

@bnb You mentioned that you had edited some of the first questions in the benchmarking survey to be less open ended. I'm still not finding that effort. Can you point me to it?

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

No branches or pull requests

7 participants