This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Add @bengl to @nodejs/security #149
Description
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.
Activity
jasnell commentedon Jun 29, 2017
ping @nodejs/ctc @nodejs/security ... definite +1 on this one. Any objections?
mcollina commentedon Jun 29, 2017
Definitely +1.
bnoordhuis commentedon Jun 29, 2017
@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 commentedon 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 commentedon Jun 29, 2017
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 commentedon Jun 29, 2017
I agree with this. Lets try to find a size that CTC is comfortable with and slim it based on your suggestion?
Trott commentedon 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.