From 7e14014bfc17447e9f2077cf5f21dbc8cc4a340a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juraci=20Paix=C3=A3o=20Kr=C3=B6hling?= Date: Fri, 25 Aug 2023 04:14:13 -0300 Subject: [PATCH 1/7] Add community values, improve code of conduct MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Juraci Paixão Kröhling --- code-of-conduct.md | 36 +++++++++++++++++++- mission-vision-values.md | 72 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 107 insertions(+), 1 deletion(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 13ef865f..20e83a18 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -1,3 +1,37 @@ # OpenTelemetry Community Code of Conduct -OpenTelemetry follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). \ No newline at end of file +The OpenTelemetry project aims to be a welcoming place where new and existing +members feel safe to respectfully share their opinions and disagreements. We +want to attract a diverse group of people to collaborate with us, which means +acknowledging that people come from different backgrounds and cultures. + +We are bound by the [CNCF Code of +Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) and +covered by that in more serious violations and prefer the reporting of +violations to be made to us as outlined below. + +## Reporting violations + +If you have seen or experienced unacceptable behavior or anything that would +make our community less welcoming, please speak up! + +The Governance Committee is the right place to bring your concerns and can be +reached via cncf-opentelemetry-governance@lists.cncf.io. You can also get in +touch with any committee member if you feel safer this way: any one of us can +receive your report and will bring it to the entire group for investigation, +anonymously if you prefer. The [current list of +members](https://github.com/open-telemetry/community/blob/main/community-members.md#governance-committee) +can be found on our community repository, and you can ping any of them directly +on [CNCF’s Slack](https://slack.cncf.io). The Governance Committee should be +diverse enough to conduct a neutral investigation having the best interests of +the project in mind at all times, and the results of the investigation will be +given back to the reporter in a timely fashion as an official position of the +GC. If you are unhappy with the outcome, you can escalate that to the CNCF via +conduct@cncf.io. Feel free to contact the CNCF directly if you have reasons to +believe that the board will not conduct a fair investigation. + +When the GC determines that a code of conduct violation happened, it will take +the actions deemed necessary and appropriate for the event. In more serious +cases, the community member might be invited to depart from our communities, +giving up any roles they may possess, such as the maintainership of a SIG. In +extreme cases, the GC can force the departure of the member. diff --git a/mission-vision-values.md b/mission-vision-values.md index e20d507d..97c5c6d4 100644 --- a/mission-vision-values.md +++ b/mission-vision-values.md @@ -116,3 +116,75 @@ to degrade gracefully as needed. OpenTelemetry users should not have to choose between high-quality telemetry and a performant application. High performance is a requirement for OpenTelemetry, and unexpected interference effects in the host application are unacceptable. + +## Community values — the principles that guide our interactions + +The OpenTelemetry project aims to be a welcoming place where new and existing +members feel safe to respectfully share their opinions and disagreements. We +want to attract a diverse group of people to collaborate with us, which means +acknowledging that people come from different backgrounds and cultures. + +There might be situations where community members act in a dubious manner. If +you have seen or experienced unacceptable behavior or anything that would make +our community less welcoming, please speak up! See [our code of +conduct](./code-of-conduct) for more information on how to report bad behavior. + +While we want to encourage everyone to express themselves in their own way, +there are some behaviors that we encourage you to adopt while interacting with +other community members. + +#### Act on behalf of the project + +It’s no secret that a good number of maintainers of the project are employed by +companies with commercial interests in OpenTelemetry, especially vendors in the +observability space. That said, we expect community members to act in the best +interests of the project. Each member’s priorities can (and should!) align with +those of their employers so that the relationship is beneficial to all parties, +but when acting as a maintainer or contributor to the project, community members +are expected to wear the project’s hat. + +##### Disclose potential conflicts of interest + +Even within the project, people might have different hats: a Collector +maintainer might be part of the Governance Committee, a JavaScript maintainer +might be part of the Technical Committee, and so on. When the context of your +message can be ambiguous, make it clear which hat you are using. For instance, +during a GC call, a person who is also a maintainer of the Collector might say: +“as a Collector maintainer, I believe that…, while as a GC member, I believe …” + +#### Assume positive intent + +We all have different priorities in our daily jobs, and while some of us are +employed to work full time on OpenTelemetry, some of us are paid to improve +specific parts of the project according to the commercial interests of our +employers. When reviewing proposals, documents, or code, take the different +perspectives into consideration, but more importantly, assume positive intent: +while the proposal might seem skewed towards a specific perspective at first, +it’s very likely that the author is open to improving it if different +perspectives are provided. + +#### Respectfully disagree + +Many decisions are made every day as part of our project. Despite giving our +best, not all decisions are the right ones. We encourage ideas and solutions to +be proposed and debated until an agreement is reached or until the “disagree and +commit” stage is reached. What we cannot tolerate is turning attacks against +ideas into attacks against people: in the heat of the moment, it might be +tempting to do an ad hominem attack but it’s always wrong. If you have reasons +to believe the person you are debating with is not acting on behalf of the +project, seek mediation instead of engaging further. While the technical merits +of the matter should be resolved within the SIG by the maintainers or, in +ultimate cases, by the Technical Committee (TC), non-technical matters should be +brought up to the Governance Committee. + +#### Be nice + +As evidenced by Erin Meyer’s [“The Cultural Map” +book](https://erinmeyer.com/books/the-culture-map/), people from different +cultural backgrounds have different ways of communicating. While we don’t expect +you to be an expert in [“reading the +air”](https://www.bbc.com/worklife/article/20200129-what-is-reading-the-air-in-japan), +we expect that you be nice to other folks and that your communication is clear +without requiring the other parties to infer what’s not explicitly written +there. This includes being minimally polite while transmitting your thoughts and +keeping snarky or inappropriate comments to yourself. From d7201742fa831953ae204d70bfa22dc9855787e9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juraci=20Paix=C3=A3o=20Kr=C3=B6hling?= Date: Fri, 25 Aug 2023 04:21:05 -0300 Subject: [PATCH 2/7] Fix link to code of conduct MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Juraci Paixão Kröhling --- mission-vision-values.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mission-vision-values.md b/mission-vision-values.md index 97c5c6d4..9ac9532c 100644 --- a/mission-vision-values.md +++ b/mission-vision-values.md @@ -127,7 +127,7 @@ acknowledging that people come from different backgrounds and cultures. There might be situations where community members act in a dubious manner. If you have seen or experienced unacceptable behavior or anything that would make our community less welcoming, please speak up! See [our code of -conduct](./code-of-conduct) for more information on how to report bad behavior. +conduct](./code-of-conduct.md) for more information on how to report bad behavior. While we want to encourage everyone to express themselves in their own way, there are some behaviors that we encourage you to adopt while interacting with From 7a04d4dca31026950b7c1704c57bba3270a85def Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juraci=20Paix=C3=A3o=20Kr=C3=B6hling?= Date: Mon, 28 Aug 2023 04:55:00 -0300 Subject: [PATCH 3/7] s/invited/requested MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Juraci Paixão Kröhling --- code-of-conduct.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 20e83a18..935282c0 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -32,6 +32,6 @@ believe that the board will not conduct a fair investigation. When the GC determines that a code of conduct violation happened, it will take the actions deemed necessary and appropriate for the event. In more serious -cases, the community member might be invited to depart from our communities, +cases, the community member might be requested to depart from our communities, giving up any roles they may possess, such as the maintainership of a SIG. In extreme cases, the GC can force the departure of the member. From 62879f4f13cf87dc3249446672f57109cfc284b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juraci=20Paix=C3=A3o=20Kr=C3=B6hling?= Date: Wed, 30 Aug 2023 06:11:07 -0300 Subject: [PATCH 4/7] Fix header levels MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Juraci Paixão Kröhling --- mission-vision-values.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/mission-vision-values.md b/mission-vision-values.md index 9ac9532c..a7a30e52 100644 --- a/mission-vision-values.md +++ b/mission-vision-values.md @@ -133,7 +133,7 @@ While we want to encourage everyone to express themselves in their own way, there are some behaviors that we encourage you to adopt while interacting with other community members. -#### Act on behalf of the project +### Act on behalf of the project It’s no secret that a good number of maintainers of the project are employed by companies with commercial interests in OpenTelemetry, especially vendors in the @@ -143,7 +143,7 @@ those of their employers so that the relationship is beneficial to all parties, but when acting as a maintainer or contributor to the project, community members are expected to wear the project’s hat. -##### Disclose potential conflicts of interest +### Disclose potential conflicts of interest Even within the project, people might have different hats: a Collector maintainer might be part of the Governance Committee, a JavaScript maintainer @@ -152,7 +152,7 @@ message can be ambiguous, make it clear which hat you are using. For instance, during a GC call, a person who is also a maintainer of the Collector might say: “as a Collector maintainer, I believe that…, while as a GC member, I believe …” -#### Assume positive intent +### Assume positive intent We all have different priorities in our daily jobs, and while some of us are employed to work full time on OpenTelemetry, some of us are paid to improve @@ -163,7 +163,7 @@ while the proposal might seem skewed towards a specific perspective at first, it’s very likely that the author is open to improving it if different perspectives are provided. -#### Respectfully disagree +### Respectfully disagree Many decisions are made every day as part of our project. Despite giving our best, not all decisions are the right ones. We encourage ideas and solutions to @@ -177,7 +177,7 @@ of the matter should be resolved within the SIG by the maintainers or, in ultimate cases, by the Technical Committee (TC), non-technical matters should be brought up to the Governance Committee. -#### Be nice +### Be nice As evidenced by Erin Meyer’s [“The Cultural Map” book](https://erinmeyer.com/books/the-culture-map/), people from different From 6d56bcae668992e915306d6a6c6147ab8ca3f43d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juraci=20Paix=C3=A3o=20Kr=C3=B6hling?= Date: Mon, 4 Sep 2023 04:47:34 -0300 Subject: [PATCH 5/7] Use full URL for CoC MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Juraci Paixão Kröhling --- mission-vision-values.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/mission-vision-values.md b/mission-vision-values.md index a7a30e52..e1746eb9 100644 --- a/mission-vision-values.md +++ b/mission-vision-values.md @@ -127,7 +127,8 @@ acknowledging that people come from different backgrounds and cultures. There might be situations where community members act in a dubious manner. If you have seen or experienced unacceptable behavior or anything that would make our community less welcoming, please speak up! See [our code of -conduct](./code-of-conduct.md) for more information on how to report bad behavior. +conduct](https://github.com/open-telemetry/community/blob/main/code-of-conduct.md) +for more information on how to report unacceptable behavior. While we want to encourage everyone to express themselves in their own way, there are some behaviors that we encourage you to adopt while interacting with @@ -179,10 +180,9 @@ brought up to the Governance Committee. ### Be nice -As evidenced by Erin Meyer’s [“The Cultural Map” -book](https://erinmeyer.com/books/the-culture-map/), people from different -cultural backgrounds have different ways of communicating. While we don’t expect -you to be an expert in [“reading the +As evidenced in [The Cultural Map](https://erinmeyer.com/books/the-culture-map/) +by Erin Meyer, people from different cultural backgrounds have different ways of +communicating. While we don’t expect you to be an expert in [“reading the air”](https://www.bbc.com/worklife/article/20200129-what-is-reading-the-air-in-japan), we expect that you be nice to other folks and that your communication is clear without requiring the other parties to infer what’s not explicitly written From cbaa46f673b88fd49b9fec8c96dc2b5f1e454079 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juraci=20Paix=C3=A3o=20Kr=C3=B6hling?= Date: Tue, 12 Sep 2023 07:17:09 -0300 Subject: [PATCH 6/7] Reorganized the code of conduct file MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Juraci Paixão Kröhling --- code-of-conduct.md | 70 +++++++++++++++++++++++++++++++--------------- 1 file changed, 47 insertions(+), 23 deletions(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 935282c0..861daf65 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -5,33 +5,57 @@ members feel safe to respectfully share their opinions and disagreements. We want to attract a diverse group of people to collaborate with us, which means acknowledging that people come from different backgrounds and cultures. -We are bound by the [CNCF Code of -Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) and -covered by that in more serious violations and prefer the reporting of -violations to be made to us as outlined below. +This project is bound by and abides by the [CNCF Code of +Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). +Conflicts should be resolved respectfully between the involved parties, however +we understand that it may not always be possible without outside help or +mediation. When needed, any community member can ask for help or report a Code +of Conduct violation to the Governance Committee as outlined below. The project +prefers that violations to be reported first to the Governance Committee so that +they may be resolved internally, however, in extreme cases code of conduct +violations should be reported to the CNCF as outlined in the [CNCF Incident +Resolution +Procedures](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-incident-resolution-procedures.md). +Anyone who is unsure if a violation should be reported to the project or the +CNCF should refer to the [CNCF CoC Jurisdiction +Policy](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committee-jurisdiction-policy.md). ## Reporting violations If you have seen or experienced unacceptable behavior or anything that would -make our community less welcoming, please speak up! +make our community less welcoming, please speak up! -The Governance Committee is the right place to bring your concerns and can be -reached via cncf-opentelemetry-governance@lists.cncf.io. You can also get in -touch with any committee member if you feel safer this way: any one of us can -receive your report and will bring it to the entire group for investigation, -anonymously if you prefer. The [current list of +When the Governing Committee (GC) determines that a code of conduct violation +happened, it will take the actions deemed necessary and appropriate for the +event. In more serious cases, the community member might be requested to depart +from our communities, giving up any roles they may possess, such as the +maintainership of a SIG. In extreme cases, the GC can force the departure of the +member. + +## Submit in writing + +To report a violation in writing, please email +cncf-opentelemetry-governance@lists.cncf.io, which goes to all GC members. If +you do not want your report to be received by all GC members, either because you +want to submit a report anonymously or because one of the GC members has a +conflict of interest, you may send your report directly to any individual GC +member. The [current list of members](https://github.com/open-telemetry/community/blob/main/community-members.md#governance-committee) can be found on our community repository, and you can ping any of them directly -on [CNCF’s Slack](https://slack.cncf.io). The Governance Committee should be -diverse enough to conduct a neutral investigation having the best interests of -the project in mind at all times, and the results of the investigation will be -given back to the reporter in a timely fashion as an official position of the -GC. If you are unhappy with the outcome, you can escalate that to the CNCF via -conduct@cncf.io. Feel free to contact the CNCF directly if you have reasons to -believe that the board will not conduct a fair investigation. - -When the GC determines that a code of conduct violation happened, it will take -the actions deemed necessary and appropriate for the event. In more serious -cases, the community member might be requested to depart from our communities, -giving up any roles they may possess, such as the maintainership of a SIG. In -extreme cases, the GC can force the departure of the member. +on [CNCF’s Slack](https://slack.cncf.io) + +## Submit in spoken conversation + +If you prefer to report the violation in a spoken conversation, you may request +a telephone conversation or virtual meeting with a GC member. + +# How to report anonymously + +If you desire to submit a report anonymously, please send a message directly to +any individual member of our GC through the CNCF Slack and let them know you +would like to submit a Code of Conduct report anonymously. If you submit your +report anonymously, that member of the GC will share the contents of your report +with the rest of the GC, but they will not disclose your identity as the +reporter to the other members of the GC (unless such disclosure is necessary to +comply with applicable laws or a court order, or to protect you or someone else +from imminent danger). From d14f264c7c7e5ff11f67a2d8188bbe3885881adb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juraci=20Paix=C3=A3o=20Kr=C3=B6hling?= Date: Wed, 20 Sep 2023 06:53:14 -0300 Subject: [PATCH 7/7] small fixes and clarifications MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Juraci Paixão Kröhling --- code-of-conduct.md | 6 +++--- mission-vision-values.md | 15 +++++++-------- 2 files changed, 10 insertions(+), 11 deletions(-) diff --git a/code-of-conduct.md b/code-of-conduct.md index 861daf65..28ceb49b 100644 --- a/code-of-conduct.md +++ b/code-of-conduct.md @@ -6,12 +6,12 @@ want to attract a diverse group of people to collaborate with us, which means acknowledging that people come from different backgrounds and cultures. This project is bound by and abides by the [CNCF Code of -Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md). +Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md). Conflicts should be resolved respectfully between the involved parties, however we understand that it may not always be possible without outside help or mediation. When needed, any community member can ask for help or report a Code of Conduct violation to the Governance Committee as outlined below. The project -prefers that violations to be reported first to the Governance Committee so that +prefers for violations to be reported first to the Governance Committee so that they may be resolved internally, however, in extreme cases code of conduct violations should be reported to the CNCF as outlined in the [CNCF Incident Resolution @@ -25,7 +25,7 @@ Policy](https://github.com/cncf/foundation/blob/main/code-of-conduct/coc-committ If you have seen or experienced unacceptable behavior or anything that would make our community less welcoming, please speak up! -When the Governing Committee (GC) determines that a code of conduct violation +When the Governance Committee (GC) determines that a code of conduct violation happened, it will take the actions deemed necessary and appropriate for the event. In more serious cases, the community member might be requested to depart from our communities, giving up any roles they may possess, such as the diff --git a/mission-vision-values.md b/mission-vision-values.md index e1746eb9..0e5646a1 100644 --- a/mission-vision-values.md +++ b/mission-vision-values.md @@ -171,8 +171,8 @@ best, not all decisions are the right ones. We encourage ideas and solutions to be proposed and debated until an agreement is reached or until the “disagree and commit” stage is reached. What we cannot tolerate is turning attacks against ideas into attacks against people: in the heat of the moment, it might be -tempting to do an ad hominem attack but it’s always wrong. If you have reasons -to believe the person you are debating with is not acting on behalf of the +tempting to make an ad hominem attack but it’s always wrong. If you have reasons +to believe the person you are debating with is not acting in the interest of the project, seek mediation instead of engaging further. While the technical merits of the matter should be resolved within the SIG by the maintainers or, in ultimate cases, by the Technical Committee (TC), non-technical matters should be @@ -182,9 +182,8 @@ brought up to the Governance Committee. As evidenced in [The Cultural Map](https://erinmeyer.com/books/the-culture-map/) by Erin Meyer, people from different cultural backgrounds have different ways of -communicating. While we don’t expect you to be an expert in [“reading the -air”](https://www.bbc.com/worklife/article/20200129-what-is-reading-the-air-in-japan), -we expect that you be nice to other folks and that your communication is clear -without requiring the other parties to infer what’s not explicitly written -there. This includes being minimally polite while transmitting your thoughts and -keeping snarky or inappropriate comments to yourself. +communicating. While we don’t expect you to be an expert in capturing unspoken +nuances, we expect that you be nice to other folks and that your communication +is clear without requiring the other parties to infer what’s not explicitly +written there. This includes being minimally polite while transmitting your +thoughts and keeping snarky or inappropriate comments to yourself.