GOVERNANCE.md (5550B)
1 ### Streams Working Group 2 3 The Node.js Streams is jointly governed by a Working Group 4 (WG) 5 that is responsible for high-level guidance of the project. 6 7 The WG has final authority over this project including: 8 9 * Technical direction 10 * Project governance and process (including this policy) 11 * Contribution policy 12 * GitHub repository hosting 13 * Conduct guidelines 14 * Maintaining the list of additional Collaborators 15 16 For the current list of WG members, see the project 17 [README.md](./README.md#current-project-team-members). 18 19 ### Collaborators 20 21 The readable-stream GitHub repository is 22 maintained by the WG and additional Collaborators who are added by the 23 WG on an ongoing basis. 24 25 Individuals making significant and valuable contributions are made 26 Collaborators and given commit-access to the project. These 27 individuals are identified by the WG and their addition as 28 Collaborators is discussed during the WG meeting. 29 30 _Note:_ If you make a significant contribution and are not considered 31 for commit-access log an issue or contact a WG member directly and it 32 will be brought up in the next WG meeting. 33 34 Modifications of the contents of the readable-stream repository are 35 made on 36 a collaborative basis. Anybody with a GitHub account may propose a 37 modification via pull request and it will be considered by the project 38 Collaborators. All pull requests must be reviewed and accepted by a 39 Collaborator with sufficient expertise who is able to take full 40 responsibility for the change. In the case of pull requests proposed 41 by an existing Collaborator, an additional Collaborator is required 42 for sign-off. Consensus should be sought if additional Collaborators 43 participate and there is disagreement around a particular 44 modification. See _Consensus Seeking Process_ below for further detail 45 on the consensus model used for governance. 46 47 Collaborators may opt to elevate significant or controversial 48 modifications, or modifications that have not found consensus to the 49 WG for discussion by assigning the ***WG-agenda*** tag to a pull 50 request or issue. The WG should serve as the final arbiter where 51 required. 52 53 For the current list of Collaborators, see the project 54 [README.md](./README.md#members). 55 56 ### WG Membership 57 58 WG seats are not time-limited. There is no fixed size of the WG. 59 However, the expected target is between 6 and 12, to ensure adequate 60 coverage of important areas of expertise, balanced with the ability to 61 make decisions efficiently. 62 63 There is no specific set of requirements or qualifications for WG 64 membership beyond these rules. 65 66 The WG may add additional members to the WG by unanimous consensus. 67 68 A WG member may be removed from the WG by voluntary resignation, or by 69 unanimous consensus of all other WG members. 70 71 Changes to WG membership should be posted in the agenda, and may be 72 suggested as any other agenda item (see "WG Meetings" below). 73 74 If an addition or removal is proposed during a meeting, and the full 75 WG is not in attendance to participate, then the addition or removal 76 is added to the agenda for the subsequent meeting. This is to ensure 77 that all members are given the opportunity to participate in all 78 membership decisions. If a WG member is unable to attend a meeting 79 where a planned membership decision is being made, then their consent 80 is assumed. 81 82 No more than 1/3 of the WG members may be affiliated with the same 83 employer. If removal or resignation of a WG member, or a change of 84 employment by a WG member, creates a situation where more than 1/3 of 85 the WG membership shares an employer, then the situation must be 86 immediately remedied by the resignation or removal of one or more WG 87 members affiliated with the over-represented employer(s). 88 89 ### WG Meetings 90 91 The WG meets occasionally on a Google Hangout On Air. A designated moderator 92 approved by the WG runs the meeting. Each meeting should be 93 published to YouTube. 94 95 Items are added to the WG agenda that are considered contentious or 96 are modifications of governance, contribution policy, WG membership, 97 or release process. 98 99 The intention of the agenda is not to approve or review all patches; 100 that should happen continuously on GitHub and be handled by the larger 101 group of Collaborators. 102 103 Any community member or contributor can ask that something be added to 104 the next meeting's agenda by logging a GitHub Issue. Any Collaborator, 105 WG member or the moderator can add the item to the agenda by adding 106 the ***WG-agenda*** tag to the issue. 107 108 Prior to each WG meeting the moderator will share the Agenda with 109 members of the WG. WG members can add any items they like to the 110 agenda at the beginning of each meeting. The moderator and the WG 111 cannot veto or remove items. 112 113 The WG may invite persons or representatives from certain projects to 114 participate in a non-voting capacity. 115 116 The moderator is responsible for summarizing the discussion of each 117 agenda item and sends it as a pull request after the meeting. 118 119 ### Consensus Seeking Process 120 121 The WG follows a 122 [Consensus 123 Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making) 124 decision-making model. 125 126 When an agenda item has appeared to reach a consensus the moderator 127 will ask "Does anyone object?" as a final call for dissent from the 128 consensus. 129 130 If an agenda item cannot reach a consensus a WG member can call for 131 either a closing vote or a vote to table the issue to the next 132 meeting. The call for a vote must be seconded by a majority of the WG 133 or else the discussion will continue. Simple majority wins. 134 135 Note that changes to WG membership require a majority consensus. See 136 "WG Membership" above.