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

update node core triage team #414

Merged
merged 7 commits into from
Jan 1, 2019
Merged

update node core triage team #414

merged 7 commits into from
Jan 1, 2019

Conversation

vdeturckheim
Copy link
Member

The people on this list are the ones who have access to the Core HackerOne program.

@bnoordhuis and @shigeki I don't see you in the HackerOne team, is this a miss?

@vdeturckheim
Copy link
Member Author

cc @nodejs/security-triage

Copy link
Member

@lirantal lirantal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@jasnell jasnell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice, I think, to use the same emeritus pattern here that we use elsewhere, rather than just removing folks.
Also, I've also pulled back from initial triage... So perhaps a section:

### Emeritus

- @bnoordhuis
- @jasnell
- @shigeki

- @indutny - **Fedor Indutny**
- @rvagg - **Rod Vagg**
- @jasnell - **James M Snell**

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jasnell Is nodejs/TSC#599 relevant here? Just confirming.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep! To be certain, I'm just stepping away from the triage bit.

@vdeturckheim
Copy link
Member Author

Good point @jasnell updating

- @indutny - **Fedor Indutny**
- @jasnell - **James M Snell**
- @mcollina - **Matteo Colina**
- @mhdawson - **Michael Dawson**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we need another list. I have access to HackerOne so that I can help with security release planning/mechanics but I don't actively triage new entries...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's just you it's probably ok to keep the current list as is instead of creating new lists (might cause confusion and noise).

@lirantal
Copy link
Member

lirantal commented Nov 1, 2018

@vdeturckheim mergable?

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mhdawson
Copy link
Member

mhdawson commented Nov 1, 2018

@bnoordhuis I have seen you have been more active lately. Should you remain on the list of triagers or does it make sense to move to emeritus?

@lirantal
Copy link
Member

LGTM
@vdeturckheim unless you (or others) want to make any further changes, I'll go ahead and merge in a couple of days.

@lirantal lirantal merged commit 92a2b78 into nodejs:master Jan 1, 2019
waveywaves pushed a commit to waveywaves/security-wg that referenced this pull request Jan 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants