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: Discuss new projects #1330

Closed
maclover7 opened this issue Jun 10, 2018 · 12 comments
Closed

Build WG: Discuss new projects #1330

maclover7 opened this issue Jun 10, 2018 · 12 comments

Comments

@maclover7
Copy link
Contributor

maclover7 commented Jun 10, 2018

This meeting will be to discuss the current state of the Build working group, as well as new projects and ideas moving forward. Everyone has a stake in the Build WG's continued success, given the critical infrastructure that the group provides.

Agenda items (please edit this liberally!):

Name Champion(s)
New members @maclover7
Ansible upgrades @maclover7, @rvagg
Commit queue @joyeecheung, @tniessen
Tracking failures in node-test-commit (nodejs/reliability, etc.) @joyeecheung
github-bot @maclover7, @phillipj
Improving current jobs @refack
Auto CI @refack, @maclover7
Automatic maintenance (allowing scripted kill and rm by anyone) @refack

@nodejs/build @nodejs/commit-queue @nodejs/tsc

@maclover7
Copy link
Contributor Author

Please RSVP via this doodle: https://doodle.com/poll/8hgewz9nem63arb7

@ryzokuken
Copy link

I hope it's okay if outsiders join in as observers? I had stuff to talk about regarding ncu-ci and the bots.

@maclover7
Copy link
Contributor Author

@ryzokuken No problem, but we will be sticking with whatever the final agenda is, given the number of topics we have to go over

@maclover7
Copy link
Contributor Author

June 19 at 4pm is one of the dates with the most options, and allows for @joyeecheung to attend, so let's plan on that being the meeting time for now

@tniessen
Copy link
Member

Something came up, I won't be able to attend that day, sorry.

@ryzokuken
Copy link

I'd love to come on as an observer today and talk about one of the things I have been talking about to @refack and @joyeecheung.

An automation for not only reporting test failures straight to the GH PRs, but more broadly to differentiate code failures from infra one, and then how to ping responsible people for infra fails (the GH path works well for code fails), and also discussion how and who to keep responsible for such stuff.

@mmarchini
Copy link
Contributor

I probably won't be able to attend as well

@refack
Copy link
Contributor

refack commented Jun 19, 2018

@mhdawson / @Trott Will you be there to broadcast?

@Trott
Copy link
Member

Trott commented Jun 19, 2018

This is today at 4PM Eastern/1PM Pacific, right? I probably can't make it as I have a conflicting meeting.

@refack
Copy link
Contributor

refack commented Jun 19, 2018

@joyeecheung
Copy link
Member

@refack
Copy link
Contributor

refack commented Jun 19, 2018

Meeting part 2
https://zoom.us/j/785639351

joyeecheung added a commit to joyeecheung/build that referenced this issue Jun 20, 2018
joyeecheung added a commit that referenced this issue Jun 20, 2018
* doc: add meeting docs for special project meeting

Fixes: #1330
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