Skip to content
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 18 April 2017 at 4 EST #683

Closed
mhdawson opened this issue Apr 13, 2017 · 13 comments
Closed

Build WG meeting 18 April 2017 at 4 EST #683

mhdawson opened this issue Apr 13, 2017 · 13 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Apr 13, 2017

Putting in this placeholder as a reminder. Will fill in details on Tuesday (Friday/Monday are a holiday for me) if nobody beats me to it.

When

Apr 18, 2017 4 PM EST - time in your timezone

Where

Agenda

Extracted from wg-agenda issues and pull requests from this repo.

All welcome of course, primarily @nodejs/build focused but we're happy to expand.

@mhdawson
Copy link
Member Author

@nodejs/build

@rvagg
Copy link
Member

rvagg commented Apr 18, 2017

Unlikely to make it this week sorry. Status:

  • Restored a couple of Pi's, pi2-2 and pi2-10 (don't have their real names at hand). Wiped and reinstalled but I'm worried about their storage, they may be faulty so we'd best keep an eye on them.
  • Pinged miniNodes and got the 3rd Odroid C2 back online
  • Did the CF log download thing, PR in this repo. Still haven't done a full validation that the data is exactly how we want it but that's 1/2 done - first pass is to turn it into nginx log format and pass it through our metrics scripts to see if they line up.
  • Pending TODO from Johan to test the LB work he's done, on the surface it looks OK but I haven't probed deeply enough to give a 👍 but if others are available to help validate then please let him know!
  • Reached out to Voxer to see if we can at least get status info on our relationship with them.
  • Still needing to make proper progress with the other macOS line of enquiry we have open, will report back soon on that.
  • Got hooked up with packet.net thanks to ARM introducing me to them - they are a SoftBank investment like ARM so have a strategic interest in server-side ARM so part of their offering is bare metal ARM64 cloud resources based on the latest server chips and it's very impressive. Myself, Johan and Michael have access to start tinkering and figuring out how best to use those resources because they're also offering general cloud resources to help us diversify which is great!

@jbergstroem
Copy link
Member

While at it; perhaps establish a standard where we use a certain emoji to indicate availability? +1/-1 or something. It would not just show if we can be there; but also if you abstain or just don't reply (general build wg activity).

@piccoloaiutante
Copy link
Member

@jbergstroem lets go 👍 and 👎 for showing who is going to attend or not..

@jbergstroem
Copy link
Member

@piccoloaiutante yeah; lets make a note about it in the meeting and add it to the 'template' for next meeting.

@piccoloaiutante
Copy link
Member

has it already started?

@joaocgreis
Copy link
Member

@piccoloaiutante no, we're waiting for the link from @mhdawson

@mhdawson
Copy link
Member Author

just about to start the hangout, 2 mins

@mhdawson
Copy link
Member Author

mhdawson commented Apr 18, 2017

@kfarnung
Copy link

I'm getting 403 forbidden for the hangouts link.

@gibfahn
Copy link
Member

gibfahn commented Apr 18, 2017

@joaocgreis
Copy link
Member

@kfarnung try removing everything after ? or the = before, worked for me once

@kfarnung
Copy link

Thanks @joaocgreis, not sure what was going on, but opening incognito worked.

gibfahn added a commit to gibfahn/build that referenced this issue Apr 19, 2017
gibfahn added a commit that referenced this issue Apr 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants