Node.js Foundation Release WorkGroup Meeting 2017-12-11 #293
Comments
|
@nodejs/Release just noticed the calendar shows a meeting for today. Probably too late notice for everybody but thought I'd create issue so we can see what is on the agenda and decide to reschedule or cancel (or if everybody can make 4 EST today (10 mins from now) do the meeting. Please comment. |
|
I'm ok with today or rescheduling. It's going to get harder to pull people together the further we push into December. |
|
Agreed. I can't make the start of the meeting today, but can likely join in 15 min or so in if everybody else decides to get together today. |
|
I'm pretty readily available so, whenever works best for other folks. Today or otherwise. |
|
I’m available today, but can do another date if neccessary
… On Dec 11, 2017, at 4:01 PM, Jeremiah Senkpiel ***@***.***> wrote:
I'm pretty readily available so, whenever works best for other folks. Today or otherwise.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub <#293 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV7sugbGwqgR2goKdkeIzxrO7Jxakks5s_Zg2gaJpZM4Q-A4v>.
|
|
20 after, we should probably just call it off and reschedule |
|
Oh no, I had it for 5pm |
|
How about tomorrow (Tuesday) at the original time 4 EST ? |
|
I'm in transit effectively all of tomorrow. |
|
wfm
… On Dec 11, 2017, at 5:03 PM, Jeremiah Senkpiel ***@***.***> wrote:
I'm in transit effectively all of tomorrow.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub <#293 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecVx5l3W7af1ArMFKG27sRmQ7m54sPks5s_aaagaJpZM4Q-A4v>.
|
|
Since @Fishrock123 is busy Tues, how about Wed at 4 EST ? |
|
Wednesday works for me too
… On Dec 11, 2017, at 5:06 PM, Michael Dawson ***@***.***> wrote:
Since @Fishrock123 <https://github.com/fishrock123> is busy Tues, how about Wed at 4 EST ?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub <#293 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV9gsbgwaIrz-3FJ06Ry46vdGQghZks5s_adWgaJpZM4Q-A4v>.
|
SGTM |
|
Ok moving to wednesday. |
|
Turns out I have a conflict with the Diagnostics WG meeting this week. I'd like to be there for any discussions on the upcoming summit so I'll miss this one. @MylesBorins can you setup the hangout for the meeting ? |
|
Since we don't have confirmation from @Fishrock123 and you can't make it and I'm not seeing anyone else chime in I'm going to suggest that we cancel. TBQH the only thing we need to meet about that can't be handled well in an issue tracker is signing off on semver-minors... but that release isn't for another month. Perhaps we should consider cancelling the standing meeting and instead holding meetings as necessary for specific issues. Thoughts? |
|
+1 to canceling standing meetings. |
|
Meetings will never happen if we do it that way around. I doubt anyone's ever going to call for a meeting. Are we ok with that? |
|
@rvagg I will personally call for meetings every time we need to review semver-minors |
|
@MylesBorins great, +1 then. |
|
Ok, I'll remove from the Foundation Calendar if we have all agreed to cancel/ |
Time
UTC Wed 13-Dec-2017 21:00 (09:00 PM):
Or in your local time:
Links
Agenda
Extracted from Release-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/Release
Invited
Observers
Notes
The agenda comes from issues labelled with
Release-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: