Skip to content

Commit

Permalink
move CODEOWNERS
Browse files Browse the repository at this point in the history
  • Loading branch information
ebullient committed Jan 10, 2024
1 parent 9658a1c commit 6accf88
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 5 deletions.
File renamed without changes.
2 changes: 1 addition & 1 deletion .mlc_config.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
"replacementPatterns": [
{
"pattern": "^CODEOWNERS",
"replacement": "{{BASEURL}}/CODEOWNERS"
"replacement": "{{BASEURL}}/.github/CODEOWNERS"
},
{
"pattern": "^TRADEMARKS",
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Ensure the PR description is clear about the changes you've made.

### 2. Await Review

One of the `CODEOWNERS` will review your PR.
One of the code owners (`.github/CODEOWNERS`) will review your PR.
We might request further clarifications, changes, or provide feedback.

### 3. Address Feedback
Expand Down
4 changes: 2 additions & 2 deletions policies/succession-plan.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,15 +34,15 @@ For libraries under heavy use, we will encourage a "path of least disturbance" a

The CF respects each project's chosen governance model. This policy complements, and does not supersede, those models. We recommend projects define:

- **Code Ownership:** Maintain a list of individuals or groups with the authority to review and merge contributions `CODEOWNERS`.
- **Code Ownership:** Maintain a list of individuals or groups with the authority to review and merge contributions (`CODEOWNERS`).

- **Project governance:** Describe project decision-making processes and contact information in `GOVERNANCE.md`. The CF must have direct contact details (kept confidential) for emergencies or coordination in the case of an extended absence.

- **Contribution guidelines:** Describe project build, test, and packaging instructions in `CONTRIBUTING.md`. Include criteria for contributions, versioning practices, and preferences in the event of an ownership transition.

Further Reading:

- `CODEOWNERS`: [About code owners][owners]
- `CODEOWNERS`: [About code owners][owners], maintained in `CODEOWNERS` or `.github/CODEOWNERS`
- `CONTRIBUTING.md`: [Wrangling Web Contributions: How to Build a CONTRIBUTING.md][contrib]. See [CONTRIBUTING.md][] and the [Project CONTRIBUTING.md template][CONTRIB-TPL] for examples.
- `GOVERNANCE.md`: See [GOVERNANCE.md][] and the [Project GOVERNANCE.md template][GOV-TPL] for examples.

Expand Down
2 changes: 1 addition & 1 deletion templates/GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ This governance model is designed to uphold the principles of transparency, open

## Roles and Responsibilities

- **Code owners:** Individuals with write access to the repository, responsible for reviewing and merging contributions, and steering project direction. These individuals (or groups) will be maintained in the repository [CODEOWNERS](CODEOWNERS) file.
- **Code owners:** Individuals with write access to the repository, responsible for reviewing and merging contributions, and steering project direction. These individuals (or groups) will be maintained in the repository (`CODEOWNERS` or `.github/CODEOWNERS`).
- **Contributors:** Anyone who contributes to the project in any form.

Reference: [About code owners](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)
Expand Down

0 comments on commit 6accf88

Please sign in to comment.