-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build WG meeting 2016-07-19 #450
Comments
Folks, due to other pressing work priorities I most likely won’t be able to attend these meetings on a regular basis. I haven’t been doing much work in build lately, and @joaocgreis has been doing a great job at handling the Windows stuff (and beyond). Secondarily, I also need to cut back on the number of late night meetings on my calendar. Would someone else be willing to facilitate these going forward? |
I'm on vacation until august, so I won't be able to join the meeting. On Friday, 15 July 2016, Alexis Campailla notifications@github.com wrote:
|
I'll be around. Although @phillipj won't be here I would still like to vote him in (unless anyone raises objections that is). |
@orangemocha I don't have access to the nodejs youtube or google account; perhaps Rod can do it? |
Yeah, I'll try and roll out of bed for this one @jbergstroem, hangout and live feed links are in OP, I haven't done document, if you have a link to the last one perhaps you can copy it, along with permissions, and make a new one for us? |
I'll set it up. |
In the future I can also help setup the meeting as I have access to the accounts. |
@mhdawson sounds good. |
Meeting Time: 8PM Tuesday July 19th UTC, or in your local timezone:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Build+WG+Meeting&iso=20160719T20&p1=%3A
Where
Agenda
Extracted from
wg-agenda
issues and pull requests from this repo.If there are any items that you would like to discuss at the meeting, please tag new or existing issues with the
wg-agenda
label, or simply post them in a comment here.All welcome of course, primarily @nodejs/build focused but we're happy to expand.
The text was updated successfully, but these errors were encountered: