Skip to content
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

Closed
MarcinHoppe opened this issue Oct 25, 2019 · 27 comments
Closed

Membership review #591

MarcinHoppe opened this issue Oct 25, 2019 · 27 comments
Assignees

Comments

@MarcinHoppe
Copy link
Contributor

MarcinHoppe commented Oct 25, 2019

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.

@vdeturckheim
Copy link
Member

I'd like to saty in.

@MarcinHoppe
Copy link
Contributor Author

I confirm that I want to remain a member of this WG.

@cjihrig
Copy link
Contributor

cjihrig commented Oct 25, 2019

I'd like to stay.

@lirantal
Copy link
Member

I'd be honored to keep working with this amazing bunch ❤️

@sam-github
Copy link
Contributor

I'd like to stay

@ronperris
Copy link
Member

I'd like to continue.

@deian
Copy link
Member

deian commented Oct 25, 2019

+1 I'd like to continue as well

@mgalexander
Copy link
Contributor

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.

@grnd
Copy link
Contributor

grnd commented Oct 26, 2019

I'd love to continue

@karenyavine
Copy link
Contributor

+1 would love to continue

@Elexy
Copy link
Contributor

Elexy commented Oct 28, 2019

-1 count me out

@pxlpnk
Copy link
Member

pxlpnk commented Oct 28, 2019

I confirm that I want to remain a member of this WG.

@mhdawson
Copy link
Member

I'd like to stay for now.

@ChALkeR
Copy link
Member

ChALkeR commented Oct 29, 2019

I'd like to continue =).

@SomeoneWeird
Copy link
Member

SomeoneWeird commented Oct 31, 2019

Would like to stay too, even though the times for our meetings are quite awkward for me :)

@MarcinHoppe
Copy link
Contributor Author

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?

@MarcinHoppe
Copy link
Contributor Author

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?

@lirantal
Copy link
Member

lirantal commented Dec 2, 2019

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?

@dgonzalez
Copy link
Member

dgonzalez commented Dec 2, 2019

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.

@MarcinHoppe
Copy link
Contributor Author

@lirantal I will reach out individually over the course of the next week and will comment on this issue.

@andreeleuterio
Copy link

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.

@bengl
Copy link
Member

bengl commented Dec 10, 2019

I don't see myself being active in this WG in the foreseeable future, so please move me to emeritus.

@lirantal
Copy link
Member

@MarcinHoppe anything else to do here? perhaps let's update per current status and run this again in 6 months time?

@MarcinHoppe
Copy link
Contributor Author

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.

@MarcinHoppe
Copy link
Contributor Author

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.

@lirantal
Copy link
Member

Yes, sounds good @MarcinHoppe and thanks for working this out

@MarcinHoppe
Copy link
Contributor Author

I created the following issues to offboard members that decided to leave the WG:

I think this issue can be closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests