-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
Comments
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. |
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. |
When does this need to be decided for? |
I'll label this tc-agenda. Unlabel if you think it's not necessary to discuss in the next TSC meeting. |
We should get this settled before June 1st, that will be before the first On Friday, May 22, 2015, Ben Noordhuis notifications@github.com wrote:
|
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? |
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. |
From the current version of https://github.com/joyent/nodejs-advisory-board/blob/master/governance-proposal/TSC-Charter-Draft.md:
Additionally, from @mikeal's interpretation @ #1416:
|
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 |
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. |
I'm referring to my role as more than just a moderator here |
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. |
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. |
+1. Sounds good. Splitting the roles is a good approach.
|
Defer to #2136 |
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
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>
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>
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>
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>
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>
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 :)
The text was updated successfully, but these errors were encountered: