doc: update TSC charter#698
Conversation
Update TSC charter to reflect merged OpenJS foundation.
jasnell
left a comment
jasnell
left a comment
There was a problem hiding this comment.
LGTM modulo the section number updates.
|
@mcollina fixed section numbering. |
|
These changes will need to be approved by either CPC or the board. |
How/when do we get clarity on which one deals with charter updates for the Node.js TSC? |
Oh, never mind, I see. Currently, it's the Node.js Board, but this changes it to the CPC. I would argue that this absolutely needs approval by both, not one or the other. (You can't take oversight away from the board without their approval.) |
Trott
left a comment
Trott
left a comment
There was a problem hiding this comment.
LGTM with minor corrections applied
Co-Authored-By: Rich Trott <rtrott@gmail.com>
Co-Authored-By: Rich Trott <rtrott@gmail.com>
Co-Authored-By: Rich Trott <rtrott@gmail.com>
|
Taken to the board and no one had concerns. We did not pass any motion or official approval, as this is something that should be done by the CPC. Added the appropriate label. @mhdawson will your tool be able to get labels from multiple orgs? |
|
@MylesBorins I don't think it is going to cross orgs. |
|
@kborchers pushed commit to address all of your comments. |
Technically, I imagine this means the board must re-approve it. In practice, I imagine they'd rather not be bothered about essentially cosmetic changes. So... ¯\(ツ)/¯ |
|
The board didn't have to approve, it was note of an FYI. If there were no
substantive changes I see no reason to bring back to the board.
…On Tue, Jun 11, 2019, 1:29 AM Rich Trott ***@***.***> wrote:
@kborchers <https://github.com/kborchers> pushed commit to address all of
your comments.
Technically, I imagine this means the board must re-approve it. In
practice, I imagine they'd rather not be bothered about essentially
cosmetic changes. So... ¯\*(ツ)*/¯
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#698?email_source=notifications&email_token=AADZYV3TYY6GMZLZ37UIKU3PZ4Z2ZA5CNFSM4HIQEDIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXL7LKA#issuecomment-500692392>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADZYV7BYP2UHUGWOVWUJX3PZ4Z2ZANCNFSM4HIQEDIA>
.
|
Co-Authored-By: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
Co-Authored-By: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
| the same person. The TSC shall hold annual elections to select a TSC | ||
| Chairperson and Director; there are no limits on the number of terms a | ||
| TSC Chairperson or Director may serve. | ||
| work on building an agenda for TSC meetings and a OpenJS |
There was a problem hiding this comment.
As an Impact project, Node.js has two voting members in CPC https://github.com/openjs-foundation/cross-project-council#impact-project-representatives
Should this be changed to two voting members?
There was a problem hiding this comment.
@trivikr no. The TSC only elects one of the two members. The second member is elected by the CommComm
| be specified by the Board relating to the intake and license compliance | ||
| review of contributions, including the Node.js Foundation IP Policy. | ||
| be specified by the OpenJS Foundation Board relating to the intake and license compliance | ||
| review of contributions, including the OpenJS Foundation IP Policy. |
There was a problem hiding this comment.
Is there an OpenJS Foundation IP Policy currently defined? If so, can this link to it?
There was a problem hiding this comment.
Ok, this should land once we get the governance update landed (7 days from now) and then we can open a PR once the links are ready.
|
This has been on TSC agenda for 2 months (less 2 days), does it still need to be? I'm prepping for the upcoming meeting, and its not clear what needs to be discussed, since this has 9 approvals, and I don't see any dissent. |
|
It's just waiting for approval by the CPC, but it does not necessarily need to be on the TSC agenda. |
|
CPC had consensus last meeting. Governance for charter updates have landed and as such this is good to land |
|
Removing from agenda because it was discussed in #731, but anyone can add the label back on if it needs to come up again. |
19 participants
Update TSC charter to reflect merged OpenJS foundation.
This cannot land until approved by the Board. (I think we need one final board approval and then subsequent approvals would be by the by the CPC?)