Node.js Foundation Community Committee (CommComm) Meeting 2017-05-11 #48
Comments
|
could i be invited as an observer, perhaps? |
|
I can't make it at that time this week, but will there be a recording? I can't remember if the TSC or CTC still do those. 😬 |
|
Can't make it, still traveling
…On May 10, 2017 5:22 PM, "Jenn Turner" ***@***.***> wrote:
I can't make it at that time this week, but will there be a recording? I
can't remember if the TSC or CTC still do those. 😬
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAecVwkIMiCUuSM33w7hGIi7-Vki-NDjks5r4cgOgaJpZM4NWOyT>
.
|
|
@nebrius Would it be possible to add a link to the Node.js calendar when posting these issues? That would be tremendously helpful. |
|
@bnb: here you go: https://calendar.google.com/calendar/embed?src=nodejs.org_nr77ama8p7d7f9ajrpnu506c98%40group.calendar.google.com. It's always in the minutes doc at the bottom, but I realize that's not super discoverable though. We might think on ways to make this better, especially since the CTC and TSC use this exact same process. EDIT: to clarify, there's a tool to generate these issues, and adding that link would involve updating the tool. It's certainly possible to do it, but it'll be slow. I have a PR sitting there that's 30 days stale 😕 |
|
@nebrius WHOOPS YEAH that's me |
|
@pup done! |
|
I do want to note to everyone that we have more folks than available spots in Hangouts right now. I don't think it'll be an issue, but worse comes to worse, we may need to ask some observers to leave to make room for members. In the future we can investigate switching to Uberconference, but my understanding is that's a bit more involved, and not something I think we should try and tackle this close to a meeting. |
|
@renrutnnej yes it will be recorded! The TSC still does, and I assume the CTC still does as well (it's supposed to anyways). |
|
Event has been created! Live stream will be at https://www.youtube.com/watch?v=NUXzn42dgjY. |
|
Feel free to remove me from the invitation on this :-) #53 |
|
oh yeah, the local time conversion links are set to 8pm, not 8:30pm @nebrius |
|
Participant link: https://hangouts.google.com/hangouts/_/qaztnwff6vhxlgxbdddilrtscue |
|
Oh whoops, sorry about the links getting messed up everyone. It starts in 10 minutes! |
|
Closing as the meeting was held and notes landed. |
|
Oh whoops, I just realized we never had a PR for the meeting notes published. Reopening for now. |
|
PR for the meeting notes: #61 |
|
Ok, now the meeting notes have been published, closing :) |
Time
UTC Thu 11-May-2017 20:30 (08:30 PM):
Or in your local time:
Links
Agenda
Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/board
nodejs/community-committee
Invited
Notes
The agenda comes from issues labelled with
cc-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
Google Hangouts; link will be posted here shortly before the meeting starts.
A standing invitation exists for all @nodejs/TSC members who are not also CommComm members to attend in observer capacity.
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
The text was updated successfully, but these errors were encountered: