VOTE: TSC Election Date

[mikeal]

Per #244 and the conversation in the last TSC Meeting, I've put together a vote. Please comment on this Issues with your preference for one of the following months:

• May
• June
• July
• August

[jasnell]

All @nodejs/tsc members... please weigh in on this. Let's see if we can reach consensus over the coming week without calling for an official vote. If we can't coalesce on a month by next Thursday I'll call for an actual vote.

Let's do it this way, assign 1, 2, 3 or 4 for each month, 1 being your first choice, 4 being your last.

Here's mine:

May	June	July	Aug
1	2	4	3

[cjihrig]

May	June	July	Aug
1	4	3	2

I ranked June and July last based on @mikeal's comment in #244, but it seems like the earlier the better.

[nebrius]

May	June	July	Aug
1	2	3	3

I'm pretty ambivalent between July and August, so I ranked them the same. That said, if they must be differentiated, then I say July=3 and August=4.

[mhdawson]

Mine

May	June	July	Aug
1	1	2	2

[Fishrock123]

May	June	July	Aug
1	2	2	3

[addaleax]

(abstaining, sorry)

[joshgav]

I vote for May, or more specifically shortly after our biannual release date (April) and with sufficient time to prepare for the next LTS (October). That's from the perspective that those who fill these roles should possess deep technical awareness and facilitate collaboration across our projects.

May	June	July	Aug
1	2	3	4

[bnoordhuis]

No strong opinion. I'm fine with May.

[rvagg]

abstain

[rvagg]

We haven't clarified the TSC & CTC chair election process either. My assumption would be that it would be undertaken at the same time but I think @nebrius was suggesting that it be done separately in #244 which might not be a bad idea. Perhaps TSC Director first, then TSC Chair after? It'd be good to clarify that while we're discussing changing the Director voting. It's up to the CTC what it wants to do but I imagine convenience would suggest alignment would be east.

[jasnell]

I think doing the vote for the TSC Director and Chair at the same time would be ideal.

[nebrius]

Just to clarify, when I said "do them separately," I didn't intend to imply they should necessarily be at separate meetings. I meant to state that they should be procedurally separate votes, but we would most likely do them back to back in the same meeting. My intent with this approach is to make sure that we dot all of our "i"s and cross all of our "t"s. After recent events surrounding by-law compliance, I think it's a good idea to be extra careful around procedures involving board seats, even if it's a bit overkill.

[rvagg]

Re timing, consider that folks may only want to hold a single position (at this stage I'd recommend it anyway I think). If we held the votes at the same time, how do we deal with a situation of someone wanting to only hold one? I'm thinking that separating them by a small amount might not be a bad idea so nominees can assess their position after the first vote, whatever that's for.

Also, aside, the next board meeting is May 30th, so you have that to shoot for if you want to have someone in place in May. A little bit of on-boarding before first meeting is probably a good idea too.

[mikeal]

@rvagg we could use Condorcet voting, https://en.wikipedia.org/wiki/Condorcet_method

That way we'd have a built in runner-up for each role. If someone only wants one of the roles the other role they were elected to would fall back to the runner-up.

[jasnell]

Given the results here, and given that there have been no objections, I think it is safe to safe that there is consensus on having the election in May. I'm going to call it and ask one more time for objections. @nodejs/tsc members: If you have any objection to holding the TSC Director and Chair election in May, please speak up now. If there are no objections raised by this time tomorrow, then I'll call it settled.

With that in mind, @mikeal and @rvagg: do you have any recommendations on how to proceed with the nominations?

[joshgav]

Per @jasnell's last comment, we have consensus to hold TSC elections in May henceforth. Thanks! Closing now.