doc: initial governance#19
Conversation
MylesBorins
force-pushed
the
basic-governance
branch
from
48efb2c to
394e3a2
Compare
| consensus. | ||
|
|
||
| If an agenda item cannot reach a consensus, a Team member can call for | ||
| the item to be decided by a vote or to table the issue to the next |
There was a problem hiding this comment.
I think it was discussed in the meeting that there will not be any "votes"
|
|
||
| If an agenda item cannot reach a consensus, a Team member can call for | ||
| to table the issue to the next meeting. The decision must be seconded by | ||
| a majority of the Team or else the discussion will continue. |
There was a problem hiding this comment.
I'd like to see a provision in here that if there are multiple choices on the table and consensus cannot be reached on one over the other, both choices are documented along with the discussion around it. This will allow us to keep iterating without blocking on any single issue.
| Pull requests must have no objections and have been open for at least 72 hours | ||
| in order to be merged into this repository. A pull request that is is unable to | ||
| reach consensus cannot be merged into this repository. | ||
|
|
There was a problem hiding this comment.
A simplified staged proposal process as suggested by Jory would be ideal here.
- Stage 0 - New Proposal
- Stage 1 - Accepted Proposal ("Accepted" in the sense that the committee has agreed to take it on)
- Stage 2 - Incorporated Proposal (Incorporated into the recommendations being made by this proposal)
As per my previous comment, if there are competing proposals that we cannot get a clear consensus on, a combined proposal that includes discussion of both should be what makes it to Stage 2.
There was a problem hiding this comment.
would you like to push a commit to incorporate these changes and I can iterate?
There was a problem hiding this comment.
Will be unable to do so until at least this afternoon or tomorrow
| It only applies to [the bootstrap repository](https://github.com/nodejs/bootstrap). | ||
|
|
||
| Pull requests must have no objections and have been open for at least 72 hours | ||
| in order to be merged into this repository. A pull request that is is unable to |
MylesBorins
force-pushed
the
basic-governance
branch
2 times, most recently
from
433c1ca to
c06ffe4
Compare
|
updated this doc to be a Stage 0 proposal. Any objections to landing as is and iterating? |
This documents the governance as discussed in the 2018-10-22 team meeting Refs: openjs-foundation#2
MylesBorins
force-pushed
the
basic-governance
branch
from
c06ffe4 to
d64f91f
Compare
|
Going to hold off on landing this until our process has been fleshed out. I feel comfortable calling this stage zero right now. I would like to move it to stage 1 or stage 2 in the next meeting |
mcollina
left a comment
mcollina
left a comment
There was a problem hiding this comment.
LGTM overall. I would move the DCO to CONTRIBUTING.md right now.
|
|
||
| The intention of the agenda is not to approve or review all patches; | ||
| that should happen continuously on GitHub and be handled by the larger | ||
| group of Collaborators. |
There was a problem hiding this comment.
I would not use the term patches here, maybe documents?
|
landing as agreed in the last meeting. We may need to refactor the proposal layout based on future PRs |
8 participants
This documents the governance as discussed in the 2018-10-22 team meeting
Refs: #2