Charter changes: remove redundancies #385
Conversation
author: @hackygolucky Original PR (reverted for further discussion): nodejs#380
Merges two paragraphs to simplify explanation of Chair + Director
|
Note that this removes reference to the individual member director /cc @williamkapke |
| @@ -24,7 +24,7 @@ Changes to CommComm membership should be posted in the agenda, and may be sugges | |||
|
|
|||
| No more than one-fourth of the CommComm members may be affiliated with the same employer or leadership of a community/ecosystem organization. If removal or resignation of a CommComm member, or a change of employment by a CommComm member, creates a situation where more than one-fourth of the CommComm membership shares an employer, then the situation must be immediately remedied by the resignation or removal of one or more CommComm members affiliated with the over-represented employer(s). | |||
|
|
|||
| The CommComm members shall consist of active members of Community Projects and the two Individual Membership Directors as defined in Section 10. | |||
| The CommComm members shall consist of active members of Community Projects and the two Individual Membership Directors. | |||
There was a problem hiding this comment.
We should remove this requirement that an Individual Membership Director is automatically a member. @williamkapke is active in CommComm as a member regardless and I think that's a much more organic approach to input and information gathering.
|
@hackygolucky and everyone else, please feel free to push changes on here. The next board meeting is next week, so it might make sense to move forward getting approval of the changes in the other PR and work out consensus for additional changes here and attempt to get this in front of the board in the next meeting. Thoughts? |
| @@ -71,7 +71,8 @@ For election of persons (CommComm Chairperson, Advisors, etc.) a multiple-candid | |||
|
|
|||
| Multiple-candidate methods may be reduced to simple election by plurality when there are only two candidates for one position to be filled. No election is required if there is only one candidate and no objections to the candidate's election. Nominations for organizations that should be represented on the Community Committee will take place in the GitHub repository. A representative for these organizations shall be selected within the organizations by those active in it. | |||
|
|
|||
| The CommComm will elect from amongst voting CommComm members a CommComm Chairperson to work on building an agenda for CommComm meetings and collaborate with the Individual Membership Directors the wishes of the CommComm to the Board for a term of one year according to the Node.js Foundation’s By-laws. The CommComm shall hold annual elections to select a CommComm Chairperson; there are no limits on the number of terms a CommComm Chairperson may serve. | |||
| The CommComm will elect from amongst voting CommComm members a CommComm Chairperson to work on building an agenda for CommComm meetings and a CommComm director to repesent the CommComm to the board for a term of one year according to the Node.js Foundation’s By-laws. The CommComm shall hold annual elections to select a CommComm Chairperson; there are no limits on the number of terms a CommComm Chairperson may serve. The | |||
| same person may not hold both positions at the same time. | |||
There was a problem hiding this comment.
Just a nit: I believe this should not be on a new separate line
| @@ -71,7 +71,8 @@ For election of persons (CommComm Chairperson, Advisors, etc.) a multiple-candid | |||
|
|
|||
| Multiple-candidate methods may be reduced to simple election by plurality when there are only two candidates for one position to be filled. No election is required if there is only one candidate and no objections to the candidate's election. Nominations for organizations that should be represented on the Community Committee will take place in the GitHub repository. A representative for these organizations shall be selected within the organizations by those active in it. | |||
|
|
|||
| The CommComm will elect from amongst voting CommComm members a CommComm Chairperson to work on building an agenda for CommComm meetings and collaborate with the Individual Membership Directors the wishes of the CommComm to the Board for a term of one year according to the Node.js Foundation’s By-laws. The CommComm shall hold annual elections to select a CommComm Chairperson; there are no limits on the number of terms a CommComm Chairperson may serve. | |||
| The CommComm will elect from amongst voting CommComm members a CommComm Chairperson to work on building an agenda for CommComm meetings and a CommComm director to repesent the CommComm to the board for a term of one year according to the Node.js Foundation’s By-laws. The CommComm shall hold annual elections to select a CommComm Chairperson; there are no limits on the number of terms a CommComm Chairperson may serve. The | |||
There was a problem hiding this comment.
typo: repesent -> "represent"
This part from line 9 is inaccurate. We need to update it 🤔 |
This part from line 23 hasn't historically been accurate – only additions to CommComm membership have been posted in the agenda. Not sure if this is something worth changing. |
This part from line 31 has historically never happened as far as I know. I suggest a modification:
|
|
@bnb since the board meeting is in two days I would like to suggest we move forward with these changes exactly as laid out and then do another round of corrections to be landed in the next board meeting. Thoughts? |
|
@MylesBorins I'm fine with that. Should I open a new PR? |
|
@bnb I know this was approved by the Board but I didn't realize we still had some questions from you. Are we good to remove the do-not-merge tag and merge this? I believe your questions are the blocker. From what I'm reading, you'd want to transfer comments from this into a new pull request as the next round of iteration. |
|
@hackygolucky yup, you can remove do-not-merge if my questions are the blocker. If we merge this I can just spin up a new PR as soon as I have time :) |
This build on top of #384, which will need to land first. Please look at
966ddef for the specific changes that are made in this PR.
The CommComm should reach consensus on this PR and then submit to the board for review.