forked from nodejs/Release
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
doc: charter the Release and LTS working group
part 1 - governance and docs for repo PR-URL: nodejs#223 Fixes: nodejs#48 Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: MichaëZasso <targos@protonmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Bartosz Sosnowski <bartosz@janeasystems.com> Reviewed-By: Rod Vagg <rod@vagg.org>
- Loading branch information
Showing
3 changed files
with
235 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| <a id="developers-certificate-of-origin"></a> | ||
| ## Developer's Certificate of Origin 1.1 | ||
|
|
||
| By making a contribution to this project, I certify that: | ||
|
|
||
| * (a) The contribution was created in whole or in part by me and I | ||
| have the right to submit it under the open source license | ||
| indicated in the file; or | ||
|
|
||
| * (b) The contribution is based upon previous work that, to the best | ||
| of my knowledge, is covered under an appropriate open source | ||
| license and I have the right under that license to submit that | ||
| work with modifications, whether created in whole or in part | ||
| by me, under the same open source license (unless I am | ||
| permitted to submit under a different license), as indicated | ||
| in the file; or | ||
|
|
||
| * (c) The contribution was provided directly to me by some other | ||
| person who certified (a), (b) or (c) and I have not modified | ||
| it. | ||
|
|
||
| * (d) I understand and agree that this project and the contribution | ||
| are public and that a record of the contribution (including all | ||
| personal information I submit with it, including my sign-off) is | ||
| maintained indefinitely and may be redistributed consistent with | ||
| this project or the open source license(s) involved. | ||
|
|
||
|
|
||
| ### Moderation Policy | ||
|
|
||
| The [Node.js Moderation Policy] applies to this WG. | ||
|
|
||
| ### Code of Conduct | ||
|
|
||
| The [Node.js Code of Conduct][] applies to this WG. | ||
|
|
||
| [Node.js Code of Conduct]: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md | ||
| [Node.js Moderation Policy]: https://github.com/nodejs/TSC/blob/master/Moderation-Policy.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,127 @@ | ||
| # Release Working Group | ||
|
|
||
| The Node.js Release Working Group (WG) maintains oversight | ||
| over the Node.js Release, Long Term Support (LTS) and | ||
| Canary in the Gold Mine (CitGM) teams. It manages the release | ||
| and long term support schedule and policies for all Node.js releases. | ||
|
|
||
| The WG has final authority over Releases including: | ||
|
|
||
| * Release process and tools. | ||
| * Content for all releases. | ||
| * Schedule for all releases. | ||
| * Contribution policy for the Release repository. | ||
| * Conduct guidelines for the Working group. | ||
| * Administration of Long Term Support policy for all releases. | ||
|
|
||
| For the current list of WG members, see the project README.md. | ||
|
|
||
| ## Collaborators | ||
|
|
||
| The Release GitHub repository is maintained by the WG (all WG | ||
| members are Collaborators for the Release repository) and additional | ||
| Collaborators who are added by the WG on an ongoing basis. | ||
|
|
||
| Individuals making significant and valuable contributions are made | ||
| Collaborators and given commit-access to the Release repository. | ||
| These individuals are identified by the WG and their addition | ||
| as Collaborators is discussed during the WG meeting. | ||
|
|
||
| **Note**: If you make a significant contribution and are not considered for | ||
| commit access, log an issue or contact a WG member directly and it will | ||
| be brought up in the next WG meeting. | ||
|
|
||
| Modifications of the contents of the Release repository are made | ||
| on a collaborative basis. Anybody with a GitHub account may propose a | ||
| modification via pull request and it will be considered by the project | ||
| Collaborators. All pull requests must be reviewed and accepted by a | ||
| Collaborator with sufficient expertise who is able to take full responsibility | ||
| for the change. In the case of pull requests proposed by an existing | ||
| Collaborator, an additional Collaborator is required for sign-off. Consensus | ||
| should be sought if additional Collaborators participate and there is | ||
| disagreement around a particular modification. See Consensus Seeking | ||
| Process below for further detail on the consensus model used for governance. | ||
|
|
||
| Collaborators may opt to elevate significant or controversial modifications, | ||
| or modifications that have not found consensus to the WG for discussion by | ||
| assigning the WG-agenda tag to a pull request or issue. The WG should serve | ||
| as the final arbiter where required. | ||
|
|
||
| ## WG Membership | ||
|
|
||
| WG seats are not time-limited. There is no fixed size of the WG. | ||
|
|
||
| There is no specific set of requirements or qualifications | ||
| for WG membership beyond these rules. | ||
|
|
||
| The WG may add additional members to the WG by consensus(defined | ||
| as no objections, more than 50% of the members participating in the | ||
| discussion, and all those participating in the discussion agreeing). | ||
|
|
||
| A WG member may be removed from the WG by voluntary resignation, | ||
| or by unanimous consensus of all other WG members. If a member is | ||
| removed from the WG then they are also removed from all WG teams | ||
| (including the Releasers team). | ||
|
|
||
| Changes to WG membership should be posted in the agenda, and may be | ||
| suggested as any other agenda item (see "WG Meetings" below). | ||
|
|
||
| If an addition or removal is proposed during a meeting, and the full WG | ||
| is not in attendance to participate, then the addition or removal is | ||
| added to the agenda for the subsequent meeting. This is to ensure | ||
| that all members are given the opportunity to participate in all | ||
| membership decisions. If a WG member is unable to attend a meeting | ||
| where a planned membership decision is being made, | ||
| then their consent is assumed. | ||
|
|
||
| No more than 1/3 of the voting WG members may be affiliated with the same | ||
| employer. If removal or resignation of a WG member, or a change of | ||
| employment by a WG member, creates a situation where more than 1/3 | ||
| of the WG membership shares an employer, then the situation must be | ||
| immediately remedied by the resignation or removal of one or more | ||
| WG members affiliated with the over-represented employer(s). | ||
|
|
||
| ## WG Meetings | ||
|
|
||
| The WG meets regularly, check the foundation calendar for details. | ||
| One of the WG members will volunteer to act as the moderator | ||
| for each meeting subject to agreement from the rest of the | ||
| members. Each meeting should be published to YouTube. | ||
|
|
||
| Items are added to the WG agenda that are considered contentious or are | ||
| modifications of governance, contribution policy, | ||
| WG 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 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, WG member or the moderator can add the item | ||
| to the agenda by adding the WG-agenda tag to the issue. | ||
|
|
||
| Prior to each WG meeting the moderator will share the Agenda with | ||
| members of the WG. WG members can add any items they like to the | ||
| agenda at the beginning of each meeting. | ||
|
|
||
| The WG may invite persons or representatives from certain | ||
| projects to participate in a non-voting capacity. | ||
|
|
||
| The moderator is responsible for summarizing the discussion of | ||
| each agenda item and sends it as a pull request after the meeting. | ||
|
|
||
| ## Consensus Seeking Process | ||
|
|
||
| The WG follows a Consensus Seeking decision-making model. | ||
|
|
||
| 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 WG 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 WG or else the | ||
| discussion will continue. Simple majority wins. | ||
|
|
||
| Note that changes to WG membership require unanimous consensus. | ||
| See "WG Membership" above. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters