Pinsave/counterstrike

1### Streams Working Group2 3The Node.js Streams is jointly governed by a Working Group4(WG)5that is responsible for high-level guidance of the project.6 7The WG has final authority over this project including:8 9* Technical direction10* Project governance and process (including this policy)11* Contribution policy12* GitHub repository hosting13* Conduct guidelines14* Maintaining the list of additional Collaborators15 16For the current list of WG members, see the project17[README.md](./README.md#current-project-team-members).18 19### Collaborators20 21The readable-stream GitHub repository is22maintained by the WG and additional Collaborators who are added by the23WG on an ongoing basis.24 25Individuals making significant and valuable contributions are made26Collaborators and given commit-access to the project. These27individuals are identified by the WG and their addition as28Collaborators is discussed during the WG meeting.29 30_Note:_ If you make a significant contribution and are not considered31for commit-access log an issue or contact a WG member directly and it32will be brought up in the next WG meeting.33 34Modifications of the contents of the readable-stream repository are35made on36a collaborative basis. Anybody with a GitHub account may propose a37modification via pull request and it will be considered by the project38Collaborators. All pull requests must be reviewed and accepted by a39Collaborator with sufficient expertise who is able to take full40responsibility for the change. In the case of pull requests proposed41by an existing Collaborator, an additional Collaborator is required42for sign-off. Consensus should be sought if additional Collaborators43participate and there is disagreement around a particular44modification. See _Consensus Seeking Process_ below for further detail45on the consensus model used for governance.46 47Collaborators may opt to elevate significant or controversial48modifications, or modifications that have not found consensus to the49WG for discussion by assigning the ***WG-agenda*** tag to a pull50request or issue. The WG should serve as the final arbiter where51required.52 53For the current list of Collaborators, see the project54[README.md](./README.md#members).55 56### WG Membership57 58WG seats are not time-limited.  There is no fixed size of the WG.59However, the expected target is between 6 and 12, to ensure adequate60coverage of important areas of expertise, balanced with the ability to61make decisions efficiently.62 63There is no specific set of requirements or qualifications for WG64membership beyond these rules.65 66The WG may add additional members to the WG by unanimous consensus.67 68A WG member may be removed from the WG by voluntary resignation, or by69unanimous consensus of all other WG members.70 71Changes to WG membership should be posted in the agenda, and may be72suggested as any other agenda item (see "WG Meetings" below).73 74If an addition or removal is proposed during a meeting, and the full75WG is not in attendance to participate, then the addition or removal76is added to the agenda for the subsequent meeting.  This is to ensure77that all members are given the opportunity to participate in all78membership decisions.  If a WG member is unable to attend a meeting79where a planned membership decision is being made, then their consent80is assumed.81 82No more than 1/3 of the WG members may be affiliated with the same83employer.  If removal or resignation of a WG member, or a change of84employment by a WG member, creates a situation where more than 1/3 of85the WG membership shares an employer, then the situation must be86immediately remedied by the resignation or removal of one or more WG87members affiliated with the over-represented employer(s).88 89### WG Meetings90 91The WG meets occasionally on a Google Hangout On Air. A designated moderator92approved by the WG runs the meeting. Each meeting should be93published to YouTube.94 95Items are added to the WG agenda that are considered contentious or96are modifications of governance, contribution policy, WG membership,97or release process.98 99The intention of the agenda is not to approve or review all patches;100that should happen continuously on GitHub and be handled by the larger101group of Collaborators.102 103Any community member or contributor can ask that something be added to104the next meeting's agenda by logging a GitHub Issue. Any Collaborator,105WG member or the moderator can add the item to the agenda by adding106the ***WG-agenda*** tag to the issue.107 108Prior to each WG meeting the moderator will share the Agenda with109members of the WG. WG members can add any items they like to the110agenda at the beginning of each meeting. The moderator and the WG111cannot veto or remove items.112 113The WG may invite persons or representatives from certain projects to114participate in a non-voting capacity.115 116The moderator is responsible for summarizing the discussion of each117agenda item and sends it as a pull request after the meeting.118 119### Consensus Seeking Process120 121The WG follows a122[Consensus123Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making)124decision-making model.125 126When an agenda item has appeared to reach a consensus the moderator127will ask "Does anyone object?" as a final call for dissent from the128consensus.129 130If an agenda item cannot reach a consensus a WG member can call for131either a closing vote or a vote to table the issue to the next132meeting. The call for a vote must be seconded by a majority of the WG133or else the discussion will continue. Simple majority wins.134 135Note that changes to WG membership require a majority consensus.  See136"WG Membership" above.137