Marc Mintel
5397309103
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 20s
Build & Deploy / 🧪 QA (push) Failing after 34s
Build & Deploy / 🏗️ Build (push) Has started running
Build & Deploy / 🚀 Deploy (push) Has been cancelled
Build & Deploy / 🧪 Smoke Test (push) Has been cancelled
Build & Deploy / ⚡ Lighthouse (push) Has been cancelled
Build & Deploy / 🔔 Notify (push) Has been cancelled
29 lines
1.2 KiB
Plaintext
29 lines
1.2 KiB
Plaintext
# `import-in-the-middle` Project Governance
|
|
|
|
## Collaborators
|
|
|
|
`import-in-the-middle` core collaborators maintain the
|
|
[nodejs/import-in-the-middle](https://github.com/nodejs/import-in-the-middle)
|
|
GitHub repository.
|
|
The GitHub team for `import-in-the-middle` core collaborators is
|
|
[@nodejs/import-in-the-middle-maintainers](https://github.com/orgs/nodejs/teams/import-in-the-middle-maintainers).
|
|
Collaborators have commit access to the
|
|
[nodejs/import-in-the-middle](https://github.com/nodejs/import-in-the-middle)
|
|
repository.
|
|
|
|
Both collaborators and non-collaborators may propose changes to the `import-in-the-middle`
|
|
source code. The mechanism to propose such a change is a GitHub pull request.
|
|
Collaborators review and merge (_land_) pull requests.
|
|
|
|
## PR Approval
|
|
|
|
Two collaborators must approve a pull request before the pull request can land.
|
|
Approving a pull request indicates that the collaborator accepts responsibility
|
|
for the change. Approval must be from collaborators who are not authors of the
|
|
change and at least one approval must be from a collaborator outside the authors
|
|
direct team.
|
|
|
|
If a collaborator opposes a proposed change, then the change cannot land. Often,
|
|
discussions or further changes result in collaborators removing their
|
|
opposition.
|