Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Add governance, CoC and contributing #107

Merged
merged 1 commit into from
Feb 4, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
# Code of Conduct

The Code of Conduct, which applies to this project, can be found at
https://github.com/nodejs/admin/blob/HEAD/CODE_OF_CONDUCT.md
34 changes: 34 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# Contributing to `require-in-the-middle`

## Code of Conduct

Please read the
[Code of Conduct](https://github.com/nodejs/admin/blob/main/CODE_OF_CONDUCT.md)
which explains the minimum behavior expectations for `require-in-the-middle` contributors.

<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.
28 changes: 28 additions & 0 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# `require-in-the-middle` Project Governance

## Collaborators

`require-in-the-middle` core collaborators maintain the
[nodejs/require-in-the-middle](https://github.com/nodejs/require-in-the-middle)
GitHub repository. The GitHub team for `require-in-the-middle` core
collaborators is
[@nodejs/require-in-the-middle-maintainers](https://github.com/orgs/nodejs/teams/require-in-the-middle-maintainers).
Collaborators have commit access to the
[nodejs/require-in-the-middle](https://github.com/nodejs/require-in-the-middle)
repository.

Both collaborators and non-collaborators may propose changes to the
`require-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.