From 1c4d9c8965952cbd17f0afdacbb0c0ac1e5bd1d7 Mon Sep 17 00:00:00 2001 From: Misty Stanley-Jones Date: Fri, 31 Mar 2017 12:49:02 -0700 Subject: [PATCH] Add diversity statement to CoC Signed-off-by: Misty Stanley-Jones --- src/main/site/xdoc/coc.xml | 46 ++++++++++++++++++++++++++++++++++---- 1 file changed, 42 insertions(+), 4 deletions(-) diff --git a/src/main/site/xdoc/coc.xml b/src/main/site/xdoc/coc.xml index e0915074a80..fc2b54907c6 100644 --- a/src/main/site/xdoc/coc.xml +++ b/src/main/site/xdoc/coc.xml @@ -32,13 +32,25 @@ under the License.

-We expect participants in discussions on the HBase project mailing lists, IRC channels, and JIRA issues to abide by the Apache Software Foundation's Code of Conduct. +We expect participants in discussions on the HBase project mailing lists, IRC +channels, and JIRA issues to abide by the Apache Software Foundation's +Code of Conduct.

-If you feel there had been a violation of this code, please point out your concerns publicly in a friendly and matter of fact manner. Nonverbal communication is prone to misinterpretation and misunderstanding. Everyone has bad days and sometimes says things they regret later. Someone else's communication style may clash with yours, but the difference can be amicably resolved. After pointing out your concerns please be generous upon receiving an apology. +If you feel there has been a violation of this code, please point out your +concerns publicly in a friendly and matter of fact manner. Nonverbal +communication is prone to misinterpretation and misunderstanding. Everyone has +bad days and sometimes says things they regret later. Someone else's +communication style may clash with yours, but the difference can be amicably +resolved. After pointing out your concerns please be generous upon receiving an +apology.

-Should there be repeated instances of code of conduct violations, or if there is an obvious and severe violation, the HBase PMC may become involved. When this happens the PMC will openly discuss the matter, most likely on the dev@hbase mailing list, and will consider taking the following actions, in order, if there is a continuing problem with an individual: +Should there be repeated instances of code of conduct violations, or if there is +an obvious and severe violation, the HBase PMC may become involved. When this +happens the PMC will openly discuss the matter, most likely on the dev@hbase +mailing list, and will consider taking the following actions, in order, if there +is a continuing problem with an individual:

  1. A friendly off-list warning;
  2. A friendly public warning, if the communication at issue was on list, otherwise another off-list warning;
    3. @@ -47,7 +59,33 @@ Should there be repeated instances of code of conduct violations, or if there is

-For flagrant violations requiring a firm response the PMC may opt to skip early steps. No action will be taken before public discussion leading to consensus or a successful majority vote. +For flagrant violations requiring a firm response the PMC may opt to skip early +steps. No action will be taken before public discussion leading to consensus or +a successful majority vote. +

+
+
+

+As a project and a community, we encourage you to participate in the HBase project +in whatever capacity suits you, whether it involves development, documentation, +answering questions on mailing lists, triaging issue and patch review, managing +releases, or any other way that you want to help. We appreciate your +contributions and the time you dedicate to the HBase project. We strive to +recognize the work of participants publicly. Please let us know if we can +improve in this area. +

+

+We value diversity and strive to support participation by people with all +different backgrounds. Rich projects grow from groups with different points of +view and different backgrounds. We welcome your suggestions about how we can +welcome participation by people at all skill levels and with all aspects of the +project. +

+

+If you can think of something we are doing that we shouldn't, or something that +we should do but aren't, please let us know. If you feel comfortable doing so, +use the public mailing lists. Otherwise, reach out to a PMC member or send an +email to the private PMC mailing list.