-
Notifications
You must be signed in to change notification settings - Fork 78
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
Membership review - still active? #217
Comments
I am still active |
I'm still here if you need me :) |
still breathing |
Also still breathing. Sometimes |
I also plan to continue being involved, I have been having time conflicts over the last few months but should be more available in Sept onward. |
still around, would like to get more involved |
Still around. More involvement again soon. |
I have not been active on the calls, probably won't have time to get back in the swing here for a while, but could come back later. I guess a move to emeritus is appropriate. I do occasionally watch the various GH traffic in the repo tho, so would like to maintain GH team membership. If it's not simple to do both of those I can be pulled from the GH team, and I'll re-request access when I get find time to collaborate here. |
I'm still around as well |
I'm active. |
I'm active.
…On Thu, 9 Aug 2018 at 14:54, Stephen Belanger ***@***.***> wrote:
I'm active.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABK2EOljuPg7-gQMMzOaD1hXVWV7fCDzks5uPK-cgaJpZM4VtE0m>
.
|
Hello, is this thing on? 🎤 |
@bnoordhuis - Ben Noordhuis This is the second reminder |
I'm not active. |
What's the path for joining? |
I'm planning on becoming more active soon, I've been taking some time off. |
As much as I'd like to be, I just can't guarantee I'll be able to dedicate any time to this wg for a while. Better move me to emeritus. |
I'm interested and working in this space, just not sure if I have the time to attend regular meetings. |
Update membership as per nodejs#217.
looks like this is actioned; closing. it makes sense to visit the membership once again, in some time |
Membership review as agreed in: #215
@AndreasMadsen - Andreas Madsen -> Active
@bnoordhuis - Ben Noordhuis
@brycebaril - Bryce Baril -> emeritus
@cjihrig - Colin Ihrig -> Active
@danielkhan - Daniel Khan -> Actrive
@dberesford - Damian Beresford
@Fishrock123 - Jeremiah Senkpiel
@Flarna - Gerhard Stöbich ->active
@hashseed - Yang Guo ->active
@hekike - Peter Marton ->active
@Hollerberg - Gernot Reisinger -> Active
@jasnell - James M Snell ->active
@jkrems - Jan Olaf Krems -> Active
@joyeecheung - Joyee Cheung ->active
@kjin - Kelvin Jin -> Active
@mcollina - Matteo Collina -> active
@mhdawson - Michael Dawson ->active
@mike-kaufman - Mike Kaufman -> active
@mmarchini - Matheus Marchini ->active
@naugtur - Zbyszek Tenerowicz ->active
@ofrobots - Ali Ijaz Sheikh -> active
@othiym23 - Forrest L Norvell -> active
@piscisaureus - Bert Belder -> emeritus
@pmuellr - Patrick Mueller -> emeritus
@Qard - Stephen Belanger -> active
@rmg - Ryan Graham -> emeritus
@sam-github - Sam Roberts -> active
@thekemkid - Glen Keane
@thlorenz - Thorsten Lorenz -> emeritus
@trevnorris - Trevor Norris
@watson - Thomas Watson -> active
@yunong - Yunong Xiao -> active
Please confirm by posting a comment on this issue if you plan to continue being active in the Diagnostics WG. If we don't hear from you we will move you to emeritus as outlined in #215 .
The text was updated successfully, but these errors were encountered: