search

nodejs / CTC

Node.js Core Technical Committee & Collaborators
80 stars 27 forks source link

Add @bengl to @nodejs/security #149

Closed bengl closed 6 years ago

bengl commented 7 years ago

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 commented 7 years ago

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

mcollina commented 7 years ago

Definitely +1.

bnoordhuis commented 7 years ago

@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 commented 7 years ago

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 commented 7 years ago

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 commented 7 years ago

@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 commented 6 years ago

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.