-
Notifications
You must be signed in to change notification settings - Fork 168
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
meta: add anonrig to build #3466
Conversation
+1 from me |
Big +1 from me. |
+1 from me |
@nodejs/build Is there anything that @anonrig or someone else should do to get this moving forward? Does anything need to happen before onboarding can begin? |
I think we can continue with onboarding (some other issues on build-agenda can probably also be handled since its been a long time since last meeting) |
Hey @MoLow, would you mind starting the onboarding to get the ball rolling? |
I don't think I have all the context yet to perform an onboarding, so definitely someone else would need to leed it |
I can lead it, no problem at all. I can include you also @mhdawson 👍. |
Onboarding to build-test issue checklist
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome!
After talking to several TSC members, I'm opening this self-nomination pull request:
I am interested in joining the Build WG to help with the current effort of understanding the infrastructure that's causing issues with our current setup. I'm also interested in getting familiar with our CI and solving outages and help improving them.
cc @MoLow @richardlau