Browse Source

Clarified wording in governance

This patch clarifies the wording on a few governance statements.
First, the intent of the rule approval policy is to encourage more
pairs of eyeballs - thus the wording was changed from +5 to 'five
positive votes'. Secondly - library upgrades should _never_ change
the existing rule set, because they already impose changes due
to bugfixes in the rules themselves.

Change-Id: I4f2765bcd04cb50da94ac121259c0cc8244bda19
Michael Krotscheck 3 years ago
parent
commit
1c762b4923
1 changed files with 3 additions and 3 deletions
  1. 3
    3
      README.md

+ 3
- 3
README.md View File

@@ -21,11 +21,11 @@ If you would like to contribute, please follow [OpenStack's contribution guideli
21 21
 
22 22
 #### Rules only land with consensus
23 23
 Patches that activate, deactivate, or modify rules, should only be merged if a consensus of
24
-reviewers is reached. In this case, consensus means at least five +1 votes, with no -1 votes. Cores 
25
-may not override and/or ignore -1 votes.
24
+reviewers is reached. In this case, consensus means at least five positive votes (+1 or +2),
25
+with no -1 votes. Cores may not override and/or ignore -1 votes.
26 26
 
27 27
 #### Library upgrades require two cores
28
-Patches that upgrade eslint only require two core approvers to land. These patches should add new
28
+Patches that upgrade eslint only require two core approvers to land. These patches must add new
29 29
 upstream rules in a deactivated state, and delete any deprecated rules.
30 30
 
31 31
 #### Policy upgrades require all cores

Loading…
Cancel
Save