-
Notifications
You must be signed in to change notification settings - Fork 122
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 #591
Comments
I'd like to saty in. |
I confirm that I want to remain a member of this WG. |
I'd like to stay. |
I'd be honored to keep working with this amazing bunch ❤️ |
I'd like to stay |
I'd like to continue. |
+1 I'd like to continue as well |
I would love to continue, but have not managed to see you guys in some time and regret that I probably will not become more available near term. Keep up the great work and I will stay as watcher to participate as/when able and please feel free to reach out if I can be of assistance. |
I'd love to continue |
+1 would love to continue |
-1 count me out |
I confirm that I want to remain a member of this WG. |
I'd like to stay for now. |
I'd like to continue =). |
Would like to stay too, even though the times for our meetings are quite awkward for me :) |
Thanks to all members who responded within the first 2 weeks! @aeleuterio @bengl @brycebaril @dgonzalez @drifkin do you plan to stay involved in this WG? |
Another 2 weeks have passed, and I think we can wrap up the annual membership review. @nodejs/security-wg we have not heard from @aeleuterio @bengl @brycebaril @dgonzalez @drifkin. Do you agree to move them all to emeritus status? |
Should we try and reach out to them individually over social as they might have been unable to get these notifications and extend this by 1 week before we move them out to emeritus? |
I'd like to stay. I need to reassess the situation on the third party modules (I don't have too much bandwidth) but I am defo interested in the security working grup. |
@lirantal I will reach out individually over the course of the next week and will comment on this issue. |
Hi folks, apologies for not replying earlier. I have not had the bandwidth to be an active member and unfortunately that will not change in the near future. I will drop now but will follow the great work you do. |
I don't see myself being active in this WG in the foreseeable future, so please move me to emeritus. |
@MarcinHoppe anything else to do here? perhaps let's update per current status and run this again in 6 months time? |
Give me 1 more week to get hold of @brycebaril and @drifkin. Then we can proceed to update the membership and offboard members who decided to step down. Then we can schedule the next review in 6 months. |
I was able to get in touch with everybody. Next step is move people who voted to leave to emeritus status. @nodejs/security-wg do you agree with tracking each departure as a separate GitHub issue with a simple checklist based on https://github.com/nodejs/security-wg/blob/master/processes/wg_offboarding.md. |
Yes, sounds good @MarcinHoppe and thanks for working this out |
I created the following issues to offboard members that decided to leave the WG:
I think this issue can be closed now. |
Before we onboard new members (#581, #582, #583), let's do an annual membership review as agreed in #302.
@aeleuterio -> responded: leaving.
@bengl -> responded: leaving.
@brycebaril -> responded: leaving.
@ChALkeR -> responded: staying.
@cjihrig -> responded: staying.
@dgonzalez -> responded: staying.
@deian -> responded: staying.
@drifkin -> responded: leaving.
@Elexy -> responded: leaving.
@grnd -> responded: staying.
@karenyavine -> responded: staying.
@lirantal -> responded: staying.
@MarcinHoppe -> responded: staying.
@mhdawson -> responded: staying.
@mgalexander -> responded: staying.
@pxlpnk -> responded: staying.
@ronperris -> responded: staying.
@sam-github -> responded: staying.
@SomeoneWeird -> responded: staying.
@vdeturckheim -> responded: staying.
Please confirm by posting a comment on this issue if you plan to continue being active in the Ecosystem Security WG. If we don't hear from you we will move you to emeritus as outlined in #302.
The text was updated successfully, but these errors were encountered: