You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We seem to have agreed on the approach for electing the CPC representatives for Node.js in nodejs/admin#316 with the process being similar to what we used for the directors so the TSC has 1 CPC voting representative to elect. The "target" date is May 1 as per openjs-foundation/cross-project-council#115.
I suggest the following timeline for the voting for the CPC representative and TSC Chair. It lines up with what we did for the TSC Chair last year (see #521) but accelerates the vote for the CPC representative in order to hit the May 1 target:
April 15 Call for nominations for both Chair and CPC representative
April 22 Close nominations and open balloting for CPC representative
April 29 Close balloting and announce CPC representative
May 1 open balloting for TSC Chair
May 15 - Announce TSC Chair representative
May 16-29- Handover
May 30 (or earlier if handover complete) Transition complete
As a related task we will also need a PR to update our governance to reflect the election of a CPC member instead of a Board representative but I think we can do that in parallel.
@mcollina I'm fine with that as well. Just chose the 15th so people would have some time to think about it before the call was open but if we don't see that as a concern we can do it earlier.
We discussed in the meeting today and agreement is that we should open the call for nominations today.
@nodejs/tsc if you are interested in running for either the position of Chair or CPC representative please nominate yourself in a comment in this issue.
@mhdawson is there a reason for running the chair ballot a week after the CPC rep ballot? seems like those can run in parallel
I can see benefit to running them separately. While I wouldn't rule it out entirely, I would be less inclined to vote for someone for Chair if they are also the CPC rep. I have no way to have that information if the elections are at the same time. (That might be OK too, although it means I'll be somewhat more likely to vote for someone running for only one of the two offices.)
@MylesBorins my main reason was to hit the target for the CPC representative (May 1) while not compressing the timeline that we use last year for the TSC Chair. I do agree @Trott's comment though in that if you run/win one position you might drop out of the second or on the flip side if you don't win the first one you might then run for the second.
At this point I think it may come down to whether we get any more candidates. For example I'm willing/interested in both positions (hence my indicating that I'd run for them), but I also know that we likely want to have 2 different people for the 2 positions given we have people to fill them.
It does say that the nominations for both do close on the 22nd so we should know at that point.
@nodejs/tsc given that only myself and @mcollina have self-nominated to run for the TSC Chair and TSC Node.js CPC representative positions I'm going to suggest that I drop out of the running for Node.js voting CPC representative. The result being that @mcollina becomes the TSC Node.js voting CPC representative and I continue as the TSC chair for another year.
Does that sound reasonable or do we still need to hold a vote or do something in addition to confirm who will hold these two positions?
Reacted by Matteo Collina, Myles Borins, Michaël Zasso, Daniel Bevenius, Anatoli Papirovski, Waleed Ashraf, Jeremiah Senkpiel and James M Snell
From gireesh punathil to Everyone: 05:38 PM
+1
From Jeremiah Senkpiel to Everyone: 05:38 PM
+1
From Anatoli to Everyone: 05:38 PM
+1
From Gabriel Schulhof to All Panelists: 05:38 PM
+1
From Sam Roberts to All Panelists: 05:39 PM
Nominations are close, right, so there can be no more candidates come forward?
+1
Activity
mhdawson commentedon Apr 8, 2019
As a related task we will also need a PR to update our governance to reflect the election of a CPC member instead of a Board representative but I think we can do that in parallel.
mcollina commentedon Apr 9, 2019
I think we should open nominations tomorrow at the TSC meeting instead.
mhdawson commentedon Apr 9, 2019
@mcollina I'm fine with that as well. Just chose the 15th so people would have some time to think about it before the call was open but if we don't see that as a concern we can do it earlier.
mhdawson commentedon Apr 10, 2019
We discussed in the meeting today and agreement is that we should open the call for nominations today.
@nodejs/tsc if you are interested in running for either the position of Chair or CPC representative please nominate yourself in a comment in this issue.
mcollina commentedon Apr 10, 2019
I'll be honoured to serve as CPC representative.
mhdawson commentedon Apr 10, 2019
I'd like to put my name in for the CPC representative and TSC Chair positions. (EDITED to say TSC Chair)
MylesBorins commentedon Apr 10, 2019
@mhdawson TSC Chair?
mhdawson commentedon Apr 11, 2019
Sorry should have been clear, CPC representative and TSC Chair.
mhdawson commentedon Apr 11, 2019
I've also edited the initial post to make it clearer that those are the 2 positions
MylesBorins commentedon Apr 15, 2019
@mhdawson is there a reason for running the chair ballot a week after the CPC rep ballot? seems like those can run in parallel
Trott commentedon Apr 15, 2019
I can see benefit to running them separately. While I wouldn't rule it out entirely, I would be less inclined to vote for someone for Chair if they are also the CPC rep. I have no way to have that information if the elections are at the same time. (That might be OK too, although it means I'll be somewhat more likely to vote for someone running for only one of the two offices.)
mhdawson commentedon Apr 15, 2019
@MylesBorins my main reason was to hit the target for the CPC representative (May 1) while not compressing the timeline that we use last year for the TSC Chair. I do agree @Trott's comment though in that if you run/win one position you might drop out of the second or on the flip side if you don't win the first one you might then run for the second.
At this point I think it may come down to whether we get any more candidates. For example I'm willing/interested in both positions (hence my indicating that I'd run for them), but I also know that we likely want to have 2 different people for the 2 positions given we have people to fill them.
It does say that the nominations for both do close on the 22nd so we should know at that point.
mhdawson commentedon Apr 22, 2019
@nodejs/tsc given that only myself and @mcollina have self-nominated to run for the TSC Chair and TSC Node.js CPC representative positions I'm going to suggest that I drop out of the running for Node.js voting CPC representative. The result being that @mcollina becomes the TSC Node.js voting CPC representative and I continue as the TSC chair for another year.
Does that sound reasonable or do we still need to hold a vote or do something in addition to confirm who will hold these two positions?
MylesBorins commentedon Apr 23, 2019
SGTM
mhdawson commentedon Apr 24, 2019
From the TSC meeting today:
From gireesh punathil to Everyone: 05:38 PM
+1
From Jeremiah Senkpiel to Everyone: 05:38 PM
+1
From Anatoli to Everyone: 05:38 PM
+1
From Gabriel Schulhof to All Panelists: 05:38 PM
+1
From Sam Roberts to All Panelists: 05:39 PM
Nominations are close, right, so there can be no more candidates come forward?
+1
mhdawson commentedon Apr 24, 2019
TSC meeting today
From Nikita Skovoroda to Everyone: 05:39 PM
+1
mhdawson commentedon Apr 24, 2019
Looks to me like we have 10/17 expressing +1 and no objections so I think we can consider us to be moving forward with:
@congralations @mcollina and thanks for taking this on.
Trott commentedon Apr 24, 2019
Seems like this issue can be closed. Re-open if I'm wrong, of course.
mcollina commentedon Apr 25, 2019
I’m stoked! Thanks for the opportunity folks!
jasnell commentedon Apr 25, 2019
Congrats to you both @mhdawson and @mcollina
(tho I do have to say, @mcollina ... aren't you supposed to be on vacation this week ;-) :-P ...)