Skip to content

Commit

Permalink
doc: copyedit GOVERNANCE.md
Browse files Browse the repository at this point in the history
PR-URL: #1963
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
  • Loading branch information
Trott committed Jun 14, 2015
1 parent 7c79490 commit 5fe6e83
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ individuals are identified by the TC and their addition as
Collaborators is discussed during the weekly TC meeting.

_Note:_ If you make a significant contribution and are not considered
for commit-access log an issue or contact a TC member directly and it
for commit-access, log an issue or contact a TC member directly and it
will be brought up in the next TC meeting.

Modifications of the contents of the iojs/io.js repository are made on
Expand Down Expand Up @@ -96,16 +96,16 @@ Items are added to the TC agenda which are considered contentious or
are modifications of governance, contribution policy, TC membership,
or release process.

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
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.

Any community member or contributor can ask that something be added to
the next meeting's agenda by logging a GitHub Issue. Any Collaborator,
TC member or the moderator can add the item to the agenda by adding
the ***tc-agenda*** tag to the issue.

Prior to each TC meeting the moderator will share the Agenda with
Prior to each TC meeting, the moderator will share the Agenda with
members of the TC. TC members can add any items they like to the
agenda at the beginning of each meeting. The moderator and the TC
cannot veto or remove items.
Expand All @@ -117,19 +117,19 @@ participate in a non-voting capacity. These invitees currently are:
chosen by that project.

The moderator is responsible for summarizing the discussion of each
agenda item and send it as a pull request after the meeting.
agenda item and sending it as a pull request after the meeting.

## Consensus Seeking Process

The TC follows a
[Consensus Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making)
decision making model.

When an agenda item has appeared to reach a consensus the moderator
When an agenda item has appeared to reach a consensus, the moderator
will ask "Does anyone object?" as a final call for dissent from the
consensus.

If an agenda item cannot reach a consensus a TC member can call for
If an agenda item cannot reach a consensus, a TC member can call for
either a closing vote or a vote to table the issue to the next
meeting. The call for a vote must be seconded by a majority of the TC
meeting. The call for a vote must be approved by a majority of the TC
or else the discussion will continue. Simple majority wins.

0 comments on commit 5fe6e83

Please sign in to comment.