From 9068dec294e0b6f9b5ec201a90b8ea6a3360637c Mon Sep 17 00:00:00 2001 From: nditada Date: Fri, 9 Sep 2016 11:32:06 -0400 Subject: [PATCH] Emojis for shorter org position --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 81a93a1..8fa3e73 100644 --- a/README.md +++ b/README.md @@ -4,10 +4,10 @@ 2. Comments on the problem and possible solutions are open and anybody can participate 3. Contributors working on a particular issue will work on a branch and submit a PR. 4. Core-team organizations can each state one position: - - Agree: The org thinks the change is possitive and approves it. - - Abstain: The org doesn't have a position on this change, but approves it. - - Disagree: The org thinks the change is negative but is willing to approve it. - - Block: The org thinkgs the change is negative and is not willing to approve it until concerns are addressed. + - :+1: Agree: The org thinks the change is possitive and approves it. + - :see_no_evil: Abstain: The org doesn't have a position on this change, but approves it. + - :-1: Disagree: The org thinks the change is negative but is willing to approve it. + - :no_entry_sign: Block: The org thinkgs the change is negative and is not willing to approve it until concerns are addressed. 5. Orgs have 1 week to comment on PRs, not necessarily stating a position. Lack of comment after one week defaults to "Abstain" position however. 6. Before 1 month, orgs have to state their position, lack of definition defaults to "Abstain". 7. To incorporate PRs into the spec, no Org has to be blocking it–i.e. all orgs have to either Agree, Abstain or Disagree.