Nominating Jeremiah Senkpiel @Fishrock123 to the TC

[mikeal]

I'd like to get some new blood on the TC. Jeremiah has been contributing to io.js for quite a while. He's a website WG member and active there. He's also been very active on the community and "house keeping" side of the project and has been quite reliable.

[Fishrock123]

o_O

[mikeal]

In case nobody noticed, I didn't speak to @Fishrock123 before I created this issue. Probably should have done that, my bad :)

[dougwilson]

The TC should have an aquarium.

[reqshark]

+1

[rvagg]

@Fishrock123 totally aside from the question of whether you want, or feel qualified for TC membership, I was also going to propose you as another _authorised releaser_ for the project, which doesn't require TC membership. Can you provide feedback in here whether you'd like to do this and if so I'll make another issue for this to go on tc-agenda and we'll see if we can make it happen.

[Fishrock123]

Can you provide feedback in here whether you'd like to do this and if so I'll make another issue for this to go on tc-agenda and we'll see if we can make it happen.

@rvagg oops, sorry, I missed that part. That mostly involves making a changelog and signing with a gpg key, right? I could do that.

[Fishrock123]

@rvagg You can open an issue for that if you'd like.

After looking over things, it's not 100% clear to me what TC responsibilities are, other than finalizing certain decisions. I'm (still) not particularly well versed with a lot of io.js internals (i think, anyways), I'm not so sure I'm reasonable to have on the TC, with my current understanding of it. (maybe it's just dev anxiety, dunno)

However, if you want me to sit in on the meetings I could. Usually I listen to the livestream anyways.

[rvagg]

@Fishrock123 the way I see it, the TC is the gatekeeper of architectural and broad API decisions and generally these will come up as a result of:

• Controversial changes that haven't reached a natural consensus here on GitHub and need a circuit breaker, currently coming in the form of people with fairly deep backgrounds in the project (but that's not absolutely essential IMO).
• Proposals for broad changes in direction, think of the idea of adopting a Promises interface and also workers: initial implementation #1159 which have fundamental impacts on what it means to be "Node" (not "Node.js").

@mikeal's proposal to expand the TC and give it new perspectives is a good one I think, just the process by which we got here is not really optimal (sorry @mikeal but I think you know this now).

The TC needs more voices with different perspectives. I for one would like to see greater representation from the types of people who are using Node heavily, currently the TC is mainly made up of people who are naturally stuck at the lower levels of Node because that's their passion and most of them are paid to do this. This is why it was sad for me to see @cjihrig resign from the TC.

The process the TC has so far established is pretty robust and should scale well when people are brought on board who are able to respect the opinions of others and defer to those who have a deeper understanding of certain topics. The real problems are going to be when the TC brings on people who don't do "team work" very well .. then we may see more tension and voting, but that's still workable.

Anyway, as for a path ahead, I think the ideal is the current suggestion of bringing you on to meetings to let you experience them and also to let the TC get comfortable with your contributions at that level.

I'll put you on the invite list for the next TC meeting.

And yes, you need to try and get over the imposter syndrome, that's not helpful to anyone.

[Fishrock123]

👍

people who are using Node heavily

However, I don't really fall under that.

[rvagg]

I'm going to put this on the agenda for voting for next meeting unless there are objections from @Fishrock123 or others. Feel free to email me privately if anybody wants to comment and doesn't feel comfortable doing so here.

[Fishrock123]

I'm going to put this on the agenda for voting for next meeting

Sure. :)