Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TSC needs to elect a board representative. #1697

Closed
mikeal opened this issue May 13, 2015 · 16 comments
Closed

TSC needs to elect a board representative. #1697

mikeal opened this issue May 13, 2015 · 16 comments
Labels
meta Issues and PRs related to the general management of the project.

Comments

@mikeal
Copy link
Contributor

mikeal commented May 13, 2015

The TSC needs to nominate and elect someone to represent them on the foundation's board of directors.

The person should have their head around the technical side of the project so that they make a good resource for the board to bounce technical questions off of and also have their head around the broader business stuff enough that they are a good resource for the TSC to ask them about the board.

First thing's first, if you're willing to do this speak up and we'll consider it a nomination. Bit of warning, board meetings are pretty boring and procedural :)

@brendanashworth brendanashworth added the meta Issues and PRs related to the general management of the project. label May 14, 2015
@piscisaureus
Copy link
Contributor

I'd be willing to do it, if there is sufficient support for it in the TC.

However we should hold off on deciding until the "merge" so the people that are coming in from the node side of things also have a chance to speak up.

@jasnell
Copy link
Member

jasnell commented May 14, 2015

Let's make sure this is on the tsc-agenda either for next week or the week after (at least to kick off the discussion, not necessarily to decide). FWIW, I would definitely support @piscisaureus as the choice.

@Fishrock123
Copy link
Contributor

When does this need to be decided for?

@bnoordhuis
Copy link
Member

I'll label this tc-agenda. Unlabel if you think it's not necessary to discuss in the next TSC meeting.

@mikeal
Copy link
Contributor Author

mikeal commented May 22, 2015

We should get this settled before June 1st, that will be before the first
board meeting.

On Friday, May 22, 2015, Ben Noordhuis notifications@github.com wrote:

I'll label this tc-agenda. Unlabel if you think it's not necessary to
discuss in the next TSC meeting.


Reply to this email directly or view it on GitHub
#1697 (comment).

@rvagg
Copy link
Member

rvagg commented May 23, 2015

seems a bit rushed for June 1st, could we have a pointer to how this role is defined? does it cycle? is there a defined scope of responsibility?

@mikeal
Copy link
Contributor Author

mikeal commented May 23, 2015

We need representation for the initial board meeting. If this seems rushed we can elect them for a limited time (like one month) so that we are set for the initial meetings.

@rvagg
Copy link
Member

rvagg commented May 28, 2015

From the current version of https://github.com/joyent/nodejs-advisory-board/blob/master/governance-proposal/TSC-Charter-Draft.md:

The TSC will elect from amongst voting TSC members a TSC Chairperson to work on building an agenda for TSC meetings and represent the TSC to the Board for a term of one year according to the Node.js Foundation’s By-laws. The TSC shall hold annual elections to select a TSC Chairperson; there are no limits on the number of terms a TSC Chairperson may serve.

Additionally, from @mikeal's interpretation @ #1416:

Charter defines a "TSC Chairperson."

  • Chairperson holds the responsibilities that io.js' current moderator holds.
  • Chairperson represents the TSC on the foundations Board of Directors
  • Chairperson is elected by TSC using Condorcet or Single Transferable Vote

@rvagg
Copy link
Member

rvagg commented Jun 3, 2015

Given that this role is also for chairperson I'd like to put my hand up as a candidate for it as well, I believe I've been mostly acting in that role of late anyway

@mikeal
Copy link
Contributor Author

mikeal commented Jun 3, 2015

The "chairperson" doesn't have to be the TSC meeting moderator, and I think we'd probably all prefer not to overload a single person with every administrative task in the TSC.

@rvagg
Copy link
Member

rvagg commented Jun 3, 2015

I'm referring to my role as more than just a moderator here

@mikeal
Copy link
Contributor Author

mikeal commented Jun 3, 2015

that's true. i'm a bit concerned with creating a role that is essentially a full time job of administrative tasks. btw, i'm working on getting a document together than outlines the responsibilities of a board member for the benefit of the election here as well as the Gold/Silver elections and the eventually Individual Member elections.

@rvagg
Copy link
Member

rvagg commented Jun 4, 2015

So, we're going to sit on this for now, please don't feel the pressure to publicly choose amongst @piscisaureus and myself. We've had a discussion about it and we both would like to be at the table for the beginning of the Foundation, not necessarily in a voting capacity though. So we're going to see if we can make this work for the short-term and have us both there even with just a single vote on behalf of the TSC. Neither of us want to do any campaigning amongst the TSC, nor do we want to force a potentially divisive vote.

We both want to propose that whatever we end up being able to make work that we do it for a short time period, 3 or 4 months seems appropriate for a settling period for the foundation. Then beyond that, when we understand the dynamics and the role better we should move on to a longer-term role, one-year between elections.

Ultimately we need someone to represent the TSC's interest clearly to the board and to communicate the board's activities and decisions back to the TSC where they impact on actual activity of the TSC (a significant amount of the of board's activity is just going to be administrativa which is of little interest to the TSC folk).

Therefore I also want to propose that we consider detaching the role of "chairperson" from "TSC board representative" as there is no good reason these need to be filled by the same person and the skill-set required for each doesn't necessarily have much overlap. But we can discuss that after the initial period as we need to get more serious about this stuff.

@jasnell
Copy link
Member

jasnell commented Jun 4, 2015

+1. Sounds good. Splitting the roles is a good approach.
On Jun 3, 2015 8:47 PM, "Rod Vagg" notifications@github.com wrote:

So, we're going to sit on this for now, please don't feel the pressure to
publicly choose amongst @piscisaureus https://github.com/piscisaureus
and myself. We've had a discussion about it and we both would like to be at
the table for the beginning of the Foundation, not necessarily in a voting
capacity though. So we're going to see if we can make this work for the
short-term and have us both there even with just a single vote on behalf of
the TSC. Neither of us want to do any campaigning amongst the TSC, nor do
we want to force a potentially divisive vote.

We both want to propose that whatever we end up being able to make work
that we do it for a short time period, 3 or 4 months seems appropriate for
a settling period for the foundation. Then beyond that, when we understand
the dynamics and the role better we should move on to a longer-term role,
one-year between elections.

Ultimately we need someone to represent the TSC's interest clearly to the
board and to communicate the board's activities and decisions back to the
TSC where they impact on actual activity of the TSC (a significant amount
of the of board's activity is just going to be administrativa which is of
little interest to the TSC folk).

Therefore I also want to propose that we consider detaching the role of
"chairperson" from "TSC board representative" as there is no good reason
these need to be filled by the same person and the skill-set required for
each doesn't necessarily have much overlap. But we can discuss that after
the initial period as we need to get more serious about this stuff.


Reply to this email directly or view it on GitHub
#1697 (comment).

@Fishrock123
Copy link
Contributor

Defer to #2136

ryzokuken added a commit to ryzokuken/node that referenced this issue Mar 6, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: nodejs#19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure
devsnek pushed a commit that referenced this issue Mar 8, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: #19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: #19161
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
targos pushed a commit that referenced this issue Mar 17, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: #19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: #19161
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
MylesBorins pushed a commit that referenced this issue Mar 20, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: #19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: #19161
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
MayaLekova pushed a commit to MayaLekova/node that referenced this issue May 8, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: nodejs#19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: nodejs#19161
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
trivikr pushed a commit to trivikr/node that referenced this issue Sep 15, 2018
Rename the test appropriately alongside mentioning the subsystem
Also, make a few basic changes to make sure the test conforms
to the standard test structure

Refs: nodejs#19105
Refs: https://github.com/nodejs/node/blob/master/doc/guides/writing-tests.md#test-structure

PR-URL: nodejs#19161
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
@KateLilly1

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

No branches or pull requests

8 participants