-
Notifications
You must be signed in to change notification settings - Fork 167
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-06-28 #438
Comments
I am going to be on vacation from June 20th to June 30th, so I won't be able to attend this one. Perhaps @mhdawson or @jbergstroem can facilitate? Note that the meeting is scheduled for June 28th. I posted the issue with more advance notice than usual |
I'm happy to facilitate, @jbergstroem unless you want to do it I'll go ahead and create the hangouts etc. |
I'm not quite sure on my whereabouts either. Can hopefully attend but I will know next week. |
Added hangouts/youtube links |
I won't make it. Sorry. I'll try to update issues tomorrow with updates. |
Hey @nodejs/build - I hope everyone got a chance to review #404 for the meeting today. It is the foundation of many tasks I'm passionately wanting to pursue. |
@williamkapke we are pretty small group in the WG meeting this week as quite a few people are away on vacation. I can see the specific action you'd like is whether the build WG can include the work to manage the bots. @jbergstroem what's your take on that based on the discussions you've had so far ? I feel like we don't want to just defer until the next meeting with William is waiting on a answer to know how to proceed. I'm not sure when everybody is back from vacation but maybe we can try to find a time to discuss this specific issue. I'll try to ping people next week to see if we have enough people back to find a time to set something up. |
PR for meeting minutes: #443 |
Thank you for the update @mhdawson. I am a big fan of taking a little of something rather than all of nothing. So I'm hoping just this WG can start with:
I am, unfortunately, a 1 man effort on the org automation parts and it isn't a flashy project- so it isn't a priority for many. So, I very much appreciate the effort to move this forward. My hope was to complete some of the org automation tasks and try to schedule some talks later this year to show them off- but I don't think that timeline will workout for that. Instead, I think I may need to try to use the time to collaborate face-to-face with anyone that will help. I will be at CascadiaFest, Node Summit, Node Interactive EU and US + Collaborator Summits, NodeConf EU... and more if anyone is interested. |
Minutes landed here: #443 |
@williamkapke have talked to @jbergstroem and he had a few ideas to pursue before getting back to you, don't think it will be too much longer. |
@mhdawson Thank you for the update! |
The plan is to get @phillipj on board and have him set it up! |
Ok I think I can close this now. |
Meeting Time: 8PM Tuesday June 28th UTC, or in your local timezone:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Build+WG+Meeting&iso=20160628T20&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: