-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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 #VI #2102
Comments
Nominating: @thefourtheye (commits) Please let us know if you'd be willing, and then available for a ~1h onboarding call. More details on times later. I'll be at CascadiaJS most of next week, but the week after might be good. |
cc @nodejs/tsc (that pesky "s"!) |
I would love to serve as a collaborator :-) |
I'd be very happy to become a collaborator ! |
+1 for @thefourtheye !! |
@thefourtheye & @targos Doodle here for times. I think I did it a little weird, never set one up before. I can do most times on these days except for Wednesday around the TSC meeting. So if you could, please put in your preferred times. The poll was created in PST but should auto-detect your timezone. If none of that works, let me know and I'll figure something else out. |
@chrisdickinson could you send me your gist? I'd like to update it a bit if you didn't already. |
@Fishrock123 in case you didn't subscribe for updates, the Doodle is complete. |
@thefourtheye @targos how about tomorrow (Friday the 17th) at 1pm PST? It should only take 45min if you're busy, but I can spend some more time to go into more detail if desired. (Also this is my first time leading an onboarding so we'll see how it goes haha) |
I'd like to suggest @joaocgreis for this list if he wants to, he's been very helpful on windows issues, particularly on the build & test side. Might be late for this one tho I suppose. |
@joaocgreis Are you able to make it tomorrow (Friday PST) at 1pm PST, or around that time? If not we'll just do you some other time soon. :) |
@Fishrock123 I can attend at 1 PM PST. |
@targos @thefourtheye @joaocgreis Actually, 2pm PST works better for me, but if that doesn't work it's ok and we'll do it at 1. (Sorry!) |
@Fishrock123 I'm fine with both |
Even I am okay to attend at 2PM PST. Anyway I stay up very late these days :D |
@Fishrock123, @thefourtheye: Note that this time of year, the west coast of the U.S. and the west coast of Canada are on PDT, not PST. If you're using the timezone abbreviation to convert to local time, you may be off by one hour if you use PST. (On the other hand, if you are relying on Doodle or some other website to do the conversion for you, then it doesn't matter and you can ignore me.) |
I'd be very happy to become a collaborator! @rvagg thanks for suggesting me! @Fishrock123 2PM PST is fine today, I'll join the meeting. |
@Fishrock123 Where do we meet? Can you confirm that the meeting is in 1h05m time (2PM PST) and not in 5m time (2PM PDT)? Thanks! |
@joaocgreis Sorry, looks like I got the timezones mixed up.. I guess it's supposed to be EDT? If you can't make now I'll do you in an hour. @targos @thefourtheye I'm running a couple minutes late, but I'll send the hangout link momentarily. |
@Fishrock123 I can, it's even better for me. Send me the link too! |
@Fishrock123 I am online and ready |
Google hangouts link: https://plus.google.com/hangouts/_/gqvncbkxr3whcsycptiequtdyya |
This one's done, thanks all! Here is the updated gist I used as a guide: https://gist.github.com/Fishrock123/8d458a00b3164f472691
|
Refer: #2102 PR-URL: #2199 Reviewed-By: Jeremiah Senkpiel <[email protected]>
@Fishrock123 Was it him? I thought it was @joaocgreis. |
@thefourtheye whoops, looks like it. |
Ref: nodejs#2102 PR-URL: nodejs#2200 Reviewed-By: Jeremiah Senkpiel <[email protected]>
Refer: #2102 PR-URL: #2208 Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Evan Lucas <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]>
I think I can run this one, since @chrisdickinson is pretty busy. :)
Thread is otherwise open for @nodejs/tc to nominate folks for onboarding as per our governance. @nodejs/collaborators, feel free to make suggestions.
Previous onboarding threads: [5], [4], [3], [2], [1].
The text was updated successfully, but these errors were encountered: