From f70d10c01d7cba1292be1508b5793c2580e88461 Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Tue, 1 Jan 2019 19:54:56 -0500 Subject: [PATCH] Updated Contributor Policies (markdown) --- Contributor-Policies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Contributor-Policies.md b/Contributor-Policies.md index b455550..cb3d1eb 100644 --- a/Contributor-Policies.md +++ b/Contributor-Policies.md @@ -2,7 +2,7 @@ This page describes general procedures for the contributors with write access to 1. Contributors should set code ownership `CODEOWNERS` files wherever they consider themselves subject-matter expects, to assist in the review process. -1. PRs to `dev` should have at least one review by a code owner before being merged. More reviews are always better, especially for large PRs. +1. PRs to `dev` should have at least one review by a code owner before being merged. If a section does not have a codeowner, any contributor may review it. More reviews are always better, especially for large PRs or if there are no defined codeowners. 1. PRs to `dev` should be merged as "Rebase and merge" to avoid a cluttered history.