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.

Sign up for GitHub

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

Jump to bottom

Membership review #313

Closed
mhdawson opened this issue Jun 14, 2018 · 25 comments
Closed

Membership review #313

mhdawson opened this issue Jun 14, 2018 · 25 comments
Assignees
@mhdawson

Comments

@mhdawson
Copy link
Member

mhdawson commented Jun 14, 2018 •
edited
Loading

Membership review as agreed in: #302.

@bengl ->confirmed, but emeritus from triage
@brycebaril -> confirmed, but emeritus from triage
@ChALkeR -> confirmed
@cjihrig -> confirmed
@dgonzalez ->confirmed
@deian ->confirmed
@digitalinfinity -> emeritus
@dougwilson -> emeritus
@drifkin -> confirmed
@evilpacket -> emeritus
@gergelyke -> emeritus
@gibfahn -> emeritus
@grnd ->confirmed
@jasnell ->emeritus
@jbergstroem -> emeritus
@joshgav -> emeritus
@lirantal -> confirmed
@MarcinHoppe -> confirmed
@mcollina -> emeritus
@mdawson ->confirmed
@mgalexander -> confirmed
@ofrobots -> emeritus
@roccomuso -> emeritus
@sam-github -> emeritus
@shigeki -> emeritus
@SomeoneWeird -> confirmed
@vdeturckheim -> confirmed

Please confirm by posting a comment on this issue if you plan to continue being active in the Security WG. If we don't hear from you we will move you to emeritus as outlined in #302.
@mhdawson mhdawson self-assigned this Jun 14, 2018
@mhdawson
Copy link
Member Author

I'm confirming that I'm planning to continue being active in the WG as requested.

@drifkin
Copy link
Contributor

drifkin commented Jun 14, 2018

I plan to continue being active.

@jasnell
Copy link
Member

jasnell commented Jun 14, 2018

I'll still be part of the security and triage team for core, but feel free to move me to emeritus status in the Security WG.

@SomeoneWeird
Copy link
Member

I still plan on helping out as much as possible 👍

@bengl
Copy link
Member

bengl commented Jun 15, 2018

Confirming that I plan to continue being active in the WG.

@vdeturckheim
Copy link
Member

I'm confirming that I'm planning to continue being active in the WG as requested.

@deian
Copy link
Member

deian commented Jun 15, 2018

Confirming to be (more) active

@MarcinHoppe
Copy link
Contributor

I confirm that I will remain an active WG member.

@dgonzalez
Copy link
Member

dgonzalez commented Jun 15, 2018 via email

@lirantal
Copy link
Member

I'm confirming that I plan to continue my activities with the WG

@grnd
Copy link
Contributor

grnd commented Jun 15, 2018

Confirming that I plan to continue being active in the WG.

@mcollina
Copy link
Member

Please move me to Emeritus status.

@mgalexander
Copy link
Contributor

I hope to get reengaged during the summer months and would like to stay an active WG member.

@shigeki
Copy link

shigeki commented Jun 15, 2018

Please move me to the emeritus list for I can only work for embargoed security patches and releases in Private Node.js core security group.

@gergelyke
Copy link
Contributor

Please move me to Emeritus status - I am still planning to be active on Slack, and help whenever I can.

@gibfahn
Copy link
Member

gibfahn commented Jun 15, 2018

Please move me to Emeritus status.

@digitalinfinity
Copy link

Please move me to Emeritus as well

@brycebaril
Copy link
Contributor

Confirming I will remain active in the security-wg, though I should probably step down from the triage team given how little time I've been able to make for that part.

@bengl
Copy link
Member

bengl commented Jun 26, 2018

I already commented stating my intention to stay on, but I think I need to join @brycebaril in stepping down from the triage team for the same reasons. If my work schedule changes in the future, I'd be happy to step in again.

@ChALkeR
Copy link
Member

ChALkeR commented Jun 26, 2018

I plan to continue being active in the Security WG.

bengl added a commit that referenced this issue Jun 27, 2018
@bengl
Move @bengl to Emeritus on 3rd-party triage team
8d1c73b 
As per #313 (comment), stepping down from the triage team mostly due to time constraints. If my work schedule changes in the future, I'd be happy to step in again.
@bengl bengl mentioned this issue Jun 27, 2018
Merged
5 tasks
@brycebaril brycebaril mentioned this issue Jun 27, 2018
Merged
5 tasks
bengl added a commit that referenced this issue Jun 29, 2018
@bengl
Move @bengl to Emeritus on 3rd-party triage team (#323)
a4dcfa6 
As per #313 (comment), stepping down from the triage team mostly due to time constraints. If my work schedule changes in the future, I'd be happy to step in again.

(I've used the "Left program" feature in HackerOne to remove myself from the team there.)

The following is a check-list for which existing WG members should be removed access from:
* [x] Remove user from [Triage Team](https://github.com/nodejs/security-wg/blob/master/processes/third_party_vuln_process.md) 
* [x] NOT REQUIRED: Remove membership from [Node.js WG Team](https://github.com/orgs/nodejs/teams/security-wg)
* [x] Remove user from [HackerOne platform](hackerone.com/nodejs-ecosystem)
* [x] Revoke any user-specific access tokens from HackerOne platform
* [x] Remove user access from private team channels in slack (nodejs-security-wg.slack.com)
@lirantal
Copy link
Member

lirantal commented Jul 2, 2018

@mcollina @jasnell @gibfahn @digitalinfinity @gergelyke can you open a PR to move yourself into emeritus?
see reference #323

@mcollina mcollina mentioned this issue Jul 3, 2018
Merged
@mcollina
Copy link
Member

mcollina commented Jul 3, 2018

@lirantal that PR you linked only refers to the 3rd-party triage team, but not this full team.

Check this out: #331

@dougwilson
Copy link
Member

Please move me to Emeritus status, as I just haven't had time to truly be active in the group :(

@mhdawson
Copy link
Member Author

mhdawson commented Jul 4, 2018

@evilpacket
@jbergstroem
@joshgav
@ofrobots
@roccomuso
@sam-github

This is the second reminder. If we don't hear from you, we'll move you to emeritus.

mhdawson added a commit to mhdawson/security-wg that referenced this issue Jul 12, 2018
@mhdawson
doc: update membershp list after review
a5ae693 
Fixes: nodejs#302
Refs: nodejs#313
@mhdawson mhdawson mentioned this issue Jul 12, 2018
Merged
mhdawson added a commit that referenced this issue Jul 17, 2018
@mhdawson
doc: update membershp list after review (#343)
ef92380 
PR-URL: #343
Fixes: #302
Refs: #313
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
@mhdawson
Copy link
Member Author

Review complete, closing.

@vdeturckheim vdeturckheim mentioned this issue Sep 18, 2018
Merged
patrickm68 added a commit to patrickm68/security-wg-process that referenced this issue Sep 14, 2023
@patrickm68
Move @bengl to Emeritus on 3rd-party triage team (#323)
f4b95a2 
As per nodejs/security-wg#313 (comment), stepping down from the triage team mostly due to time constraints. If my work schedule changes in the future, I'd be happy to step in again.

(I've used the "Left program" feature in HackerOne to remove myself from the team there.)

The following is a check-list for which existing WG members should be removed access from:
* [x] Remove user from [Triage Team](https://github.com/nodejs/security-wg/blob/master/processes/third_party_vuln_process.md) 
* [x] NOT REQUIRED: Remove membership from [Node.js WG Team](https://github.com/orgs/nodejs/teams/security-wg)
* [x] Remove user from [HackerOne platform](hackerone.com/nodejs-ecosystem)
* [x] Revoke any user-specific access tokens from HackerOne platform
* [x] Remove user access from private team channels in slack (nodejs-security-wg.slack.com)
patrickm68 added a commit to patrickm68/security-wg-process that referenced this issue Sep 14, 2023
@patrickm68
doc: update membershp list after review (#343)
e1662d4 
PR-URL: nodejs/security-wg#343
Fixes: nodejs/security-wg#302
Refs: nodejs/security-wg#313
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
mattstern31 added a commit to mattstern31/security-wg-process that referenced this issue Nov 11, 2023
@mattstern31
Move @bengl to Emeritus on 3rd-party triage team (#323)
99f404f 
As per nodejs/security-wg#313 (comment), stepping down from the triage team mostly due to time constraints. If my work schedule changes in the future, I'd be happy to step in again.

(I've used the "Left program" feature in HackerOne to remove myself from the team there.)

The following is a check-list for which existing WG members should be removed access from:
* [x] Remove user from [Triage Team](https://github.com/nodejs/security-wg/blob/master/processes/third_party_vuln_process.md) 
* [x] NOT REQUIRED: Remove membership from [Node.js WG Team](https://github.com/orgs/nodejs/teams/security-wg)
* [x] Remove user from [HackerOne platform](hackerone.com/nodejs-ecosystem)
* [x] Revoke any user-specific access tokens from HackerOne platform
* [x] Remove user access from private team channels in slack (nodejs-security-wg.slack.com)
mattstern31 added a commit to mattstern31/security-wg-process that referenced this issue Nov 11, 2023
@mattstern31
doc: update membershp list after review (#343)
9aa85cc 
PR-URL: nodejs/security-wg#343
Fixes: nodejs/security-wg#302
Refs: nodejs/security-wg#313
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mhdawson mhdawson

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests