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.

Sign up for GitHub

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

Jump to bottom

Node.js Foundation Build WorkGroup Meeting 2017-12-05 #1028

Closed
mhdawson opened this issue Dec 3, 2017 · 16 comments
Closed

Node.js Foundation Build WorkGroup Meeting 2017-12-05 #1028

mhdawson opened this issue Dec 3, 2017 · 16 comments
Assignees
@mhdawson @gibfahn

Comments

@mhdawson
Copy link
Member

mhdawson commented Dec 3, 2017 •
edited
Loading

Time

UTC Tue 05-Dec-2017 23:00 (11:00 PM):

Timezone Date/Time
US / Pacific Tue 05-Dec-2017 15:00 (03:00 PM)
US / Mountain Tue 05-Dec-2017 16:00 (04:00 PM)
US / Central Tue 05-Dec-2017 17:00 (05:00 PM)
US / Eastern Tue 05-Dec-2017 18:00 (06:00 PM)
Amsterdam Wed 06-Dec-2017 00:00 (12:00 AM)
Moscow Wed 06-Dec-2017 02:00 (02:00 AM)
Chennai Wed 06-Dec-2017 04:30 (04:30 AM)
Hangzhou Wed 06-Dec-2017 07:00 (07:00 AM)
Tokyo Wed 06-Dec-2017 08:00 (08:00 AM)
Sydney Wed 06-Dec-2017 10:00 (10:00 AM)

Or in your local time:

Links

Agenda

Extracted from build-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/build

  • New OSX infra walkthrough #1026
  • Provide read access to our ci.nodejs.org configs #972
  • Ubuntu non-LTS strategy #967
  • Remove ARM64 Ubuntu 14.04 X-Gene servers from CI #966
  • Remove Fedora 22, 23, 24 #962
  • Remove Ubuntu 12.04 #961
  • Make it easier for people to join the Build WG #941
  • Permission to start culling all pre-v4 infra and build logic #926
  • suggestion: investigate a commit-queue solution #705
  • Versions of OSX to support #705

Invited

  • Build team: @nodejs/build

Observers

Notes

The agenda comes from issues labelled with build-agenda across 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
@mhdawson mhdawson self-assigned this Dec 3, 2017
@maclover7
Copy link
Contributor

Should be able to be there.

Not sure if there's time this meeting, but would like to give a run through of some of the blue ocean stuff I've been playing around with to the group.

@Trott
Copy link
Member

Trott commented Dec 3, 2017

Oh, wow, I think I can make this one! Since the Testing WG is no longer a thing, I wonder if this is the right group to bring up the unreliable tests and try to assemble a small group of people with the right skills to fix them. Probably not this meeting though as the agenda looks pretty full.

@gibfahn
Copy link
Member

gibfahn commented Dec 4, 2017

Not sure if there's time this meeting, but would like to give a run through of some of the blue ocean stuff I've been playing around with to the group.

What we've done before with some success is to just have people stay on if they can (and are interested). Meeting ends at midnight for me, so getting late, but I'd like to stay on and discuss it.

@joyeecheung
Copy link
Member

I'll try my best to wake up in time to attend

@richardlau
Copy link
Member

Meeting ends at midnight for me, so getting late, but I'd like to stay on and discuss it.

In which case the two "Or in your local time:" links are incorrect unless the meeting is really going to go on for four hours (both links convert to 8pm UTC). @mhdawson @gibfahn

@kfarnung
Copy link

kfarnung commented Dec 4, 2017

@mhdawson It looks like the "in your local time" links still point to 8pm UTC rather than 11pm UTC.

@mhdawson
Copy link
Member Author

mhdawson commented Dec 4, 2017

@kfarnung I'm guessing that that must be a problem with https://github.com/nodejs/make-node-meeting as it is used to generate the template.. I see its the case for all of the meetings generated not just this one. @rvagg looks like the time is hardcoded to 8 UTC for those 2 links.

@mhdawson
Copy link
Member Author

mhdawson commented Dec 4, 2017

I see there is already an issue open for this: nodejs/make-node-meeting#28

@Trott
Copy link
Member

Trott commented Dec 4, 2017 •
edited
Loading

I've edited the "in your local time" links above to correct them.

@richardlau
Copy link
Member

@Trott The links should be 11pm UTC not am.

@Trott
Copy link
Member

Trott commented Dec 5, 2017

@Trott The links should be 11pm UTC not am.

Re-edited.

@refack
Copy link
Contributor

refack commented Dec 5, 2017

ping?

@Trott
Copy link
Member

Trott commented Dec 5, 2017

I just joined on the Uberconference line, but that's clearly wrong...

@mhdawson
Copy link
Member Author

mhdawson commented Dec 5, 2017

Starting meeting now, will paste link in a min

@mhdawson
Copy link
Member Author

mhdawson commented Dec 5, 2017

https://hangouts.google.com/hangouts/_/ytl/cR6eoQNN0dAS2Yfp4ZbMUM6GxNTVUMPbmHfXBbvpfI8=?eid=100598160817214911030

@joyeecheung
Copy link
Member

joyeecheung commented Dec 6, 2017 •
edited
Loading

My alert failed me so didn't make it..sorry!

@gibfahn gibfahn self-assigned this Dec 13, 2017
gibfahn added a commit to gibfahn/build that referenced this issue Dec 13, 2017
@gibfahn
doc: add minutes for 2017-12-05
a7b1024 
This is the first meeting to use the new auto-generated template, so we
should see what needs adding.

Fixes: nodejs#1028
@gibfahn gibfahn mentioned this issue Dec 13, 2017
Merged
gibfahn added a commit to gibfahn/build that referenced this issue Dec 13, 2017
@gibfahn
doc: add minutes for 2017-12-05
884510d 
This is the first meeting to use the new auto-generated template, so we
should see what needs adding.

Fixes: nodejs#1028
gibfahn added a commit that referenced this issue Jan 3, 2018
@gibfahn
doc: add minutes for 2017-12-05 (#1042)
f6af20e 
This is the first meeting to use the new auto-generated template, so we
should see what needs adding.

Fixes: #1028
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mhdawson mhdawson

@gibfahn gibfahn

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@refack @Trott @kfarnung @maclover7 @joyeecheung @richardlau @mhdawson @gibfahn