-
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: Discuss new projects #1330
Comments
Please RSVP via this doodle: https://doodle.com/poll/8hgewz9nem63arb7 |
I hope it's okay if outsiders join in as observers? I had stuff to talk about regarding |
@ryzokuken No problem, but we will be sticking with whatever the final agenda is, given the number of topics we have to go over |
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 |
Something came up, I won't be able to attend that day, sorry. |
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. |
I probably won't be able to attend as well |
This is today at 4PM Eastern/1PM Pacific, right? I probably can't make it as I have a conflicting meeting. |
Meeting part 2 |
* doc: add meeting docs for special project meeting Fixes: #1330
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!):
node-test-commit
(nodejs/reliability
, etc.)github-bot
kill
andrm
by anyone)@nodejs/build @nodejs/commit-queue @nodejs/tsc
The text was updated successfully, but these errors were encountered: