-
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 self-nomination: amiller-gh #1305
Comments
@amiller-gh Our next build WG meeting is scheduled for 4pm EST / 8pm UTC on June 12 -- if you're not fully onboarded by then, please feel free to join anyways. Once this gets a few more +1s, then we can begin that process! |
Happily! Its on my calendar 👍 |
Is that a recurring meeting time that I should block off? |
@amiller-gh The time rotates every few weeks (I forget what the different variations are off the top of my head), but all meetings for the build WG (and all other Node.js Foundation stuff) are listed in the foundation calendar https://calendar.google.com/calendar/embed?src=nodejs.org_nr77ama8p7d7f9ajrpnu506c98%40group.calendar.google.com |
@amiller-gh Are you still interested in joining the Build WG? I'm happy to have a chat here or one-on-one in some other medium (my email is in my GitHub profile) if you have questions or anything like that. |
Hey Rich! Sorry, just got back from my month-long trip. Finally starting to get through my backlog – will email you in the next 24h to sync 👍 |
/ping @nodejs/build How can we move forward with this? Adam works at LinkedIn and is involved in the Community Committee and the Website redesign. |
I'm not sure if we have a defined process, but getting involved with the WG is just a matter of learning how it works and being given accesses. Seems like the easiest way to proceed would be for Adam to join the meetings and have a read through the documentation in this repo. There are hopefully some tasks that could be picked up without requiring too much access. Maybe one thing we could do is go through an onboarding without actually adding Adam to the WG (yet), that way they could get an overview of how things work in the short term. |
I've been remiss in being unable to attend the last two meetings. Will be sure to rearrange my schedule accordingly to get more deeply involved. I've already read through most of the docs in the repo and will try to find a good first ticket to bang my head against until next meeting 👍 |
Is there a blocker on the Node.js side that we could identify that might clear a path for @amiller-gh to be more involved? |
@amiller-gh anything that you would identify in terms of @Trott's question? |
Oh my this is still open? Nothing blocking other than my own packed schedule... Going to close this - I unfortunately still don't have the cycles to get more deeply involved with Build at this time 🙏 |
@amiller-gh approached me about Build WG membership so they could help out with CI stuff. I'm making a note here so that there's a logical place for them to ping if I forget to continue the conversation later.
The text was updated successfully, but these errors were encountered: