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

Review membership #302

Closed
mhdawson opened this issue Jun 5, 2018 · 6 comments
Closed

Review membership #302

mhdawson opened this issue Jun 5, 2018 · 6 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Jun 5, 2018

It may be time to review our membership list. There are quite a few people that I don't think have been active for quite a while. It is probably a good time to do this as the WG is being formally chartered.

What I'd suggest is:

  1. Post an issue with an @ notice to all members asking they confirm they still plan to be active in the WG.
  2. Remind after 2 weeks
  3. After 4 weeks move all of those who have not responded to 'emeritus'
  4. Allow a grace period of 4 more weeks where people can request to be added back without requiring consensus reaching by the WG.

@nodejs/security-wg thoughts?

@vdeturckheim
Copy link
Member

LGTM!

@MarcinHoppe
Copy link
Contributor

I suspect that after all grace periods elapse, all the access rights will be revoked for emeritus WG members? It would be good to compile list of action items before we have to do it.

@mhdawson
Copy link
Member Author

mhdawson commented Jun 6, 2018

@MarcinHoppe, correct. Starting list would be:

  1. Update README.md
  2. remove from https://github.com/orgs/nodejs/teams/security-wg

@mhdawson
Copy link
Member Author

mhdawson commented Jun 6, 2018

Possibly also remove from security-wg slack ? @lirantal. @vdeturckheim

@mhdawson
Copy link
Member Author

mhdawson commented Jun 6, 2018

We should also likely remove hacker one access if the team member had it.

@vdeturckheim
Copy link
Member

@mhdawson
We can remove them from the private channels and H1 as needed yes. @lirantal and I are admin on both and should be able to do so.

mhdawson added a commit to mhdawson/security-wg that referenced this issue Jul 12, 2018
mhdawson added a commit that referenced this issue Jul 17, 2018
PR-URL: #343
Fixes: #302
Refs: #313
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
patrickm68 added a commit to patrickm68/security-wg-process that referenced this issue Sep 14, 2023
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
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
Projects
None yet
Development

No branches or pull requests

3 participants