-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
governance: add new collaborators #IV #1057
Comments
Nominating @jbergstroem and @petkaantonov. |
@bnoordhuis nominated my nominations! I'll try and go back through PRs and find anyone else we're missing out on. |
@Fishrock123 s'ok to nominate, you probably need a seconder from TC. I'm not TC but I second your @silverwind and will leave it to @chrisdickinson to decide how to go forward with these. |
Thanks for the nomination. I'm honoured and accept. Being honest, I see myself contributing more to the build WC than this one, but they intersect a fair amount since test suite and platform conformance is of big interest to me. Also, having a collaborator flag makes it easier to help with issue/pr triaging. |
@jbergstroem precisely, if you look at most of my contributions to core since the fork they have been largely focused around tests & build and I see you doing the same so we need to ease the friction on that. I expect that @kenperkins and @geek may fall in to the same category and for similar reasons I still want to see @othiym23 made a collaborator! |
Nominating @bnoordhuis to nominate people. |
What about @yosuke-furukawa? |
@tellnes thanks!!! I would like to join :D |
I'm up for this. Thanks for the suggestion / implicit assignment of more work, @rvagg! 😁 |
I'd be glad to join and work on |
@othiym23 bah, you're doing npm here anyway so this is just an extension of that, not much more work |
@silverwind +1 |
Thanks for nominating, folks. Would the following people be willing to fill out this doodle with your availability? All times are PST, if you can't make it let me know (via email, at chris at neversaw dot us) and I can expand the number of times. The meeting runs 45 minutes to 1 hour long and covers how to use the issue tracker, CI, merging PRs, local setup, and general M.O. of the project. There'll be time for questions during the meeting, or if you'd like to ask ahead of time via email that's totally fine too. The day of the meeting (once decided) I'll email hangout invites and meeting notes to you shortly beforehand. Thanks! Your help is much appreciated. |
The onboarding will happen at 10AM PDT (click here for local time), March 17th. You'll get an email (at the address listed on your github account) shortly beforehand with a google hangouts link and meeting notes. Thanks! See you then. |
Ok, the emails have gone out. If you didn't get an invite, please ping me in IRC (chrisdickinson on freenode) and I'll DM you the URL. Thanks! |
Onboarding hangout just ended. Thanks for your time, everyone! |
It's that time again! I'd like to open up the floor for @iojs/tc to nominate folks for the next onboarding. Lots of great work has been done from folks in the last few weeks, so there's no shortage of folks to nominate :)
At the end of the week I'll put together a doodle and add it to this thread for nominees to respond to.
Thanks all!
Previously, previously, previously.
The text was updated successfully, but these errors were encountered: