chore(team): write governance

CONTRIBUTING.md

@@ -145,7 +145,8 @@ When submitting a pull request:
 ### Acceptance Criteria
 
 For a pull request to be merged, it must:
-- Receive approval from at least 2 reviewers
+- Receive approval from at least 2 reviewers with write access
+- Receive no objections from reviewers with write access
 - Pass all tests
 - Be open for at least 48 hours to allow for review and discussion
   - except hotfixes and trivial corrections (like typos)

GOVERNANCE.md

@@ -0,0 +1,62 @@
+# Governance
+
+Meet the current members of the Node.js userland migrations:
+
+- [@AugustinMauroy](https://github.com/AugustinMauroy) - **Augustin Mauroy** (he/him)
+- [@avivkeller](https://github.com/avivkeller) - **Aviv Keller** (he/him)
+- [@bmuenzenmeyer](https://github.com/bmuenzenmeyer) - **Brian Muenzenmeyer** (he/him)
+- [@JakobJingleheimer](https://github.com/JakobJingleheimer) - **Jacob Smith** (he/him) - Maintainer
+- [@ljharb](https://github.com/ljharb) - **Jordan Harband** (he/him)
+
+## Rights
+
+Any team member can block a pull request or decision. A block can be overturned by a team vote, which requires a quorum of two-thirds of active members and passes with a simple majority (>50%). Pursuant to Node.js policy, the [TSC](https://github.com/nodejs/TSC) may override a team’s vote.
+Any member can create a tag on the repository's `HEAD` branch, which triggers a CI run and initiates a release. Tags must follow the format `vX.Y.Z@workspace`, where `X.Y.Z` is the version number and `workspace` is the name of the npm workspace (e.g. `v1.2.3@codemod`).
+
+### Active vs inactive membership
+
+### Retaining Membership
+
+Members are expected to engage in project discussions regularly, and members inactive for more than six months may be removed from the active members list. Removed members can be reinstated upon returning to active participation.
+
+The team lead is not more equal than other active members; it is an administrative function. For administrative purposes, the lead owns the repo, the github team, and handles membership changes and repository administration (particularly potentially destructive actions).
+
+The team lead is responsible for ensuring team policies are followed, and takes some discretion when taking administrative action (such as removing an inactive member per team policy).
+
+The team lead can also bypass Github Branch rulesets to merge PRs that are otherwise blocked by the rules (such as for trivial edits/corrects and hot-fixes).
+
+## Team nomination
+
+This policy extends the parent Node.js policy.
+
+Current Node.js collaborators are free to join at any time and do not require a nomination.
+
+Current Node.js members who are not collaborators are free to request to join without a nomination or meeting contribution criteria. The request must have no objections after 3 days. All active members must be notified of the request.
+
+Non-members of the Node.js org should meet the following criteria:
+
+- ~2 months of consistent (substantive, non-trivial) contribution/participation.
+  - _Consistent_ means roughly once a week (we all have lives)
+  - _Substantive_ means adds value and does not detract from the issue at hand.
+
+Exceptions may be made for members of the larger ecosystem who are well known to the Node.js organisation.
+
+An active member may nominate a contributor who meets this criteria. The nomination must pass before requesting the contributor be added to the organisation. All active members must be notified of the nomination.
+
+A nomination should be raised privately with active members before publicly, out of respect for the nominee.
+
+### Team Maintainers
+
+Team maintainers serve in an administrative capacity and are not considered "more equal" than other active contributors. Their primary role is to support smooth project operations.
+
+Maintainership includes responsibilities such as managing the GitHub repository and team, handling membership changes, and performing administrative tasks, especially those that may be destructive or sensitive in nature.
+
+Maintainers ensure team policies are upheld and may exercise discretion when taking necessary actions, such as removing inactive members in accordance with team guidelines.
+
+Additionally, maintainers have the ability to bypass GitHub branch protection rules to merge pull requests, typically in cases of trivial edits, urgent corrections, or hot-fixes.
+
+## Team Expulsion
+
+A team member who violates Node.js's code of conduct or who is acting against the interests or mandate of the team, or acts in bad faith may be expelled by vote of the team; such a vote requires a quorum of ⅔ of active members passing by ⅗ super majority. If a vote passes a simple majority but fails a super majority, the team member will be asked to voluntarily exit. Expulsion votes are confidential and are not conveyed to the expulee (they may be verified in confidence by the TSC).
+
+When expulsion proceedings are commenced, team membership is frozen until the vote has settled.