Ohm-Management - Projektarbeit B-ME
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

GOVERNANCE.md 5.4KB

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