-
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 2015-12-01 #269
Comments
|
re arm/mips: I have a tessel 2 at my office. Not doing too much at the moment since running tests on it is painful. So far I'm looking into their build system as well as compile testing. |
The meeting is confirmed for tomorrow (Tuesday). Hangout on air for participants: https://plus.google.com/events/ck9tfcvpo3aq2sc5c2k3dr0lqpc |
It seems like the link is to view the meeting not join |
Meeting minutes are here: https://docs.google.com/document/d/1zFMmIYUP1tA_YS_sx7P0-vZQ3zy3sOYGSG73otRvoSc/edit |
Meeting was had. |
This commit adds the following notes: - 2015-12-01 (#269) - 2015-12-22 (#283) - 2016-01-12 (#300) - 2016-02-02 (#313) - 2016-02-23 (#336) - 2016-03-15 (#351) PR-URL: #388 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Signed-off-by: Hans Kristian Flaatten <[email protected]>
This is a request for agenda items for the next occurrence of the Build WG meeting.
Meeting Time: 8PM Tuesday December 1st UTC, or in your local timezone:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Build+WG+Meeting&iso=20151201T20&p1=%3A
Hangout on air for participants: https://plus.google.com/events/ck9tfcvpo3aq2sc5c2k3dr0lqpc
To watch: http://www.youtube.com/watch?v=9aVNXVazrVw
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: