Skip to content

Latest commit

 

History

History
150 lines (106 loc) · 6.12 KB

GOVERNANCE.md

File metadata and controls

150 lines (106 loc) · 6.12 KB
Raw

Web-Server Frameworks Team

For the current list of Team members, see the project README.md.

Members

The nodejs/web-server-frameworks GitHub repository is maintained by the Team and additional Members who are added on an ongoing basis.

Team Membership

Team Membership is not time-limited. There is no fixed size of the Team.

There is no specific set of requirements or qualifications for Team Membership beyond these rules.

Prospective members should request membership though a PR labelled membership-request which adds them to the Team membership list. The PR will be merged in accordance with the pull request consensus process.

Team membership will be revisited every 6 months. A PR will be open moving members without any activity in the past 6 months to a Past Collaborators list. Members can comment on the PR to keep themselves in the members list. The PR will be merged in 7 days in accordance with the pull request consensus process.

Past collaborators may rejoin the Team using the same process specified above for prospective members.

Team Meetings

The Team meets bi-weekly on Zoom.us. A designated moderator approved by the Team runs the meeting. Each meeting should be published to YouTube.

Items are added to the Team agenda that are considered contentious or are modifications of governance, contribution policy, Team 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, Team member or the moderator can add the item to the agenda by adding the web-server-frameworks-agenda tag to the issue.

Prior to each Team meeting the moderator will share the agenda with members of the Team. Team members can add any items they like to the agenda at the beginning of each meeting. The moderator and the Team cannot veto or remove items.

The Team may invite persons or representatives from certain projects to participate in a non-voting capacity.

Decisions made in meetings must go through the pull request consensus process. One of the members present in the meeting will be responsible for opening the PR, if one doesn't exist already.

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 Team 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 Team member can call for the item to be decided by a vote or to table the issue to the next meeting. In both cases the decision must be seconded by a majority of the Team or else the discussion will continue. Simple majority wins. Only Active Members participate in a vote.

Pull Requests

Pull requests that do not change the governance of the team or remove members can be merged into this repository provided the following conditions have been met:

  • There are no outstanding objections
  • There are two approvals by team members
  • The PR has been open for at least 48 hours

Pull requests that change governance of the team or remove members must meet the following conditions in addition to the ones listed for regular PRs.

  • The PR has been open for at least 7 days.

If consensus cannot be reached, a pull request may still be landed after a vote by the members to override outstanding objections.

Fast-Tracking PRs

Special exception is made for pull requests seeking to make any of the following changes to this repository:

  • Errata fixes.
  • Editorial changes.
  • Meeting minutes.
  • Updates to the team lists.
  • Doc Fixes.

To propose fast-tracking a pull request, apply the fast-track label. Then add a comment that members may upvote.

If someone disagrees with the fast-tracking request, remove the label. Do not fast-track the pull request in that case.

The pull request may be fast-tracked if two members approve the fast-tracking request. To land, the pull request itself still needs two member approvals.

Members may request fast-tracking of pull requests they did not author. In that case only, the request itself is also one fast-track approval. Upvote the comment anyway to avoid any doubt.

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.