Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Add @bengl to @nodejs/security #149

Closed
bengl opened this issue Jun 29, 2017 · 7 comments
Closed

Add @bengl to @nodejs/security #149

bengl opened this issue Jun 29, 2017 · 7 comments

Comments

@bengl
Copy link
Member

bengl commented Jun 29, 2017

I'd like to be added to the @nodejs/security team. I couldn't find any defined process for inclusion in the team (and maybe that's something that needs to be addressed), so @jasnell suggested I should just ask here in an issue on CTC. I'm a Node.js collaborator working at a Node.js security company, and it would be nice if we could be as up-to-date as possible with the security-happenings and contribute to the best of our ability.

@jasnell
Copy link
Member

jasnell commented Jun 29, 2017

ping @nodejs/ctc @nodejs/security ... definite +1 on this one. Any objections?

@mcollina
Copy link
Member

Definitely +1.

@bnoordhuis
Copy link
Member

@nodejs/security is already bigger than is responsible, IMO. Access should be on a need-to-know basis, which, sorry @bengl, as far as I can see doesn't apply to you.

@rvagg
Copy link
Member

rvagg commented Jun 29, 2017

I kind of agree with Ben here, sorry to say, we need to be a bit more careful in widening this particular tent. We already have a bunch of members that are deriving more value from inclusion than providing and what we need is clear additive value.

@jasnell
Copy link
Member

jasnell commented Jun 29, 2017

We already have a bunch of members that are deriving more value from inclusion than providing

Perhaps what we need, then, is to rotate some folks out in favor of bringing in new individuals who have a higher likelihood of participation.

@jbergstroem
Copy link
Member

@jasnell said:
Perhaps what we need, then, is to rotate some folks out in favor of bringing in new individuals who have a higher likelihood of participation.

I agree with this. Lets try to find a size that CTC is comfortable with and slim it based on your suggestion?

@Trott
Copy link
Member

Trott commented Sep 8, 2017

This repo isn't active anymore, but perhaps @bengl would like to open this in the TSC repo? Either way, I'm going to close this.

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

No branches or pull requests

7 participants