-
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 2017-10-24 22:00 pm UTC #939
Comments
Could we talk a bit the option of adding people to the WG without direct ssh access, but more geared towards helping the Automating SIG? (Also about having some DevOps sandbox machines, and even a sandbox Jenkins)? |
@refack will raise issue. |
@joyeecheung and @maclover7, as prospective members it'd be great if you could attend, assuming you have time. I know it's a bit last minute. We should probably extend the invitation to anyone in nodejs/automation who's willing (join if you'd like). However I'd like to make sure everyone in build is okay with that before inviting, so we can discuss at this meeting and plan for next time if no objections. |
IMHO we should first talk in the current format about changing the format... |
@nodejs/automation ping, anyone's welcome to join this meeting in ~45 mins and we can discuss how Build can best support Automation efforts and what an optimal relationship might be between the two groups. |
I might be late to this, I have a quick but important meeting scheduled shortly beforehand |
@rvagg Could I get an invite? |
@ev1stensberg someone should post a link to the hangout a couple of minutes before it starts. Speaking of which, @mhdawson are you hosting today? |
not sure if meeting has started yet, but is not streaming on youtube |
We're "cat herding" |
on now |
When
Oct 24, 2017 22:00 UTC - time in your timezone
Where
Agenda
Extracted from
wg-agenda
issuesand pull requests from this repo.
All welcome of course, primarily @nodejs/build focused but we're happy to expand.
Please 👍 if you can make the meeting, and 👎 if you cannot.
The text was updated successfully, but these errors were encountered: