Guiding principles, concerns, general operations#9
Conversation
| and provide specific feedback on: | ||
|
|
||
| 1. Whether the merger should proceed | ||
| 2. What the overall structure of a merged Foundation should look like |
There was a problem hiding this comment.
if we label each item 1. github markdown will automate numbering. Good way to future proof.
| 2. What the overall structure of a merged Foundation should look like | ||
| 3. How projects should be organized within a merged Foundation | ||
| 4. What representation projects should have on a merged Foundation's Board of | ||
| Directors |
There was a problem hiding this comment.
maybe add what the name of the organization should be
| ### Contributing to this repository | ||
|
|
||
| Anyone may contribute to this repository via pull request. All individuals | ||
| holding commit rights to any Node.js Foundatioon or JS Foundation project may |
There was a problem hiding this comment.
s/Foundatioon/Foundation
| Anyone may contribute to this repository via pull request. All individuals | ||
| holding commit rights to any Node.js Foundatioon or JS Foundation project may | ||
| participate in the Node+JS Bootstrap Committee and may request commit access | ||
| to this repository. |
There was a problem hiding this comment.
I think we should have an explicit +1 from someone representing the JSF for this. I don't see any conflicts, but would be good to have explicit buy in
perhaps @dmethvin or jorydotcom
| ### Committee Co-Chairs | ||
|
|
||
| Committee Co-Chairs should be selected by vote of the available Committee | ||
| Membership. |
There was a problem hiding this comment.
As Committee Membership above is described as all members with commit rights to any Node.js or JSF project how will we be able to properly manage a vote?
Should we allow open membership to anyone meeting that criteria and the vote would be help by active members?
There was a problem hiding this comment.
The other aspect that should be covered here is who can volunteer? If it is any member then we should say that specifically.
7fc4325 to
4e11bc3
Compare
| The Committee does not vote. Should it become impossible to determine consensus | ||
| on a given issue, each of the contending positions should be documented within | ||
| the repository with the arguments for and against each clearly documented for | ||
| further consideration. |
There was a problem hiding this comment.
From your comments, what you suggest is that the final decisions will be made by the board/foundation staff. If that is the case then I think you should state that here clearly. ie if the bootstrap committee cannot come to a consensus then we document the divergent opinions and the board/foundation staff will make the decision.
There was a problem hiding this comment.
That is still not clear from the suggested text.
|
I'll review those over the next couple of days and will see what updates can be made here. It's going to take some time because of the travel and prep for nodeconfeu |
|
Np, just in the process of doing review myself
… On Nov 2, 2018, at 7:17 PM, James M Snell ***@***.***> wrote:
I'll review those over the next couple of days and will see what updates can be made here. It's going to take some time because of the travel and prep for nodeconfeu
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV-HgL8_zuL3TrtYjkxiibv1SeZN6ks5urNJtgaJpZM4XcwzK>.
|
|
@jasnell are you open to removing the |
|
Yes that's fine |
|
@jasnell are you still planning to pursue this or can it be closed? |
This is a proposed alternative to the takes in #7, #1, and #4 ...
This takes a first stab at connecting the discussions that are happening now with the principles that guided the launch of the foundation in the first place; establishes a process for identifying who is a part of this committee and how decisions are made; and begins to address some of the community concerns that have been raised.