As announced on gcc@. --- htdocs/bugs/index.html | 3 + htdocs/conduct-faq.html | 66 ++++++++++++++++ htdocs/conduct-report.html | 122 ++++++++++++++++++++++++++++++ htdocs/conduct-response.html | 141 +++++++++++++++++++++++++++++++++++ htdocs/conduct.html | 118 +++++++++++++++++++++++++++++ htdocs/index.html | 3 + htdocs/lists.html | 2 + 7 files changed, 455 insertions(+) create mode 100644 htdocs/conduct-faq.html create mode 100644 htdocs/conduct-report.html create mode 100644 htdocs/conduct-response.html create mode 100644 htdocs/conduct.html
diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index aaef8915..6dbe5d45 100644 --- a/htdocs/bugs/index.html +++ b/htdocs/bugs/index.html @@ -122,6 +122,9 @@ three of which can be obtained from the output of <code>gcc -v</code>:</p> <li>Questions about the correctness or the expected behavior of certain constructs that are not GCC extensions. Ask them in forums dedicated to the discussion of the programming language.</li> + + <li>Violations of the <a href="conduct.html">Code of Conduct</a>.</li> + </ul> <h3 id="where">Where to post it</h3> diff --git a/htdocs/conduct-faq.html b/htdocs/conduct-faq.html new file mode 100644 index 00000000..867527e8 --- /dev/null +++ b/htdocs/conduct-faq.html @@ -0,0 +1,66 @@ +<!DOCTYPE html> +<html lang="en"> + +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +<meta name="description" content="GCC project Code of Conduct"> +<meta name="keywords" + content="GCC, conduct"> +<title>GCC Code of Conduct FAQ</title> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css";> +</head> + +<body> +<h1><a href="conduct.html">GCC Code of Conduct</a> FAQ</h1> + +<h3>Why adopt a Code of Conduct?</h3> +<p>The vast majority of the time, the GCC community is a very civil, +cooperative space. On the rare occasions that it isn't, it's helpful to have +something to point to to remind people of our expectations. It's also good for +newcomers to have something to refer to, for both how they are expected to +conduct themselves and how they can expect to be treated.</p> + +<p>More importantly, if there is offensive behavior that isn't addressed +immediately, it's important for there to be a way to report that to the project +leadership so that we can intervene.</p> + +<h3>Why not just refer to the GNU Kind Communication Guidelines?</h3> +<p>The Guidelines are helpful for establishing the kind of behavior we want to +see, but it's also important to have a reporting mechanism to help people feel +safe and supported in the community, and to help leadership to hear about +problems that might otherwise have escaped their notice.</p> + +<h3>Shouldn't people try to work problems out between themselves first?</h3> +<p>Certainly, in many cases. And we hope referring to the CoC might be helpful +then, as well. If the problem is successfully resolved, no report is +necessary, though individuals might still want to let the CoC committee know +about the incident just for their information.</p> + +<h3>What about the rights of the reportee?</h3> +<p>The CoC committee will get their perspective, and any other available +information, before taking any action.</p> + +<p>Besides which, we expect the response to the vast majority of incidents to +be email asking those involved to moderate their behavior. That has been the +experience of other free software projects after adopting a code of conduct: +see the <a href="https://www.kernel.org/code-of-conduct.html";>Linux Kernel +CoC</a> reports for an example.</p> + +<h3>Is this going to be used to drive out people with "wrong" opinions?</h3> +<p>No, this is a code of <strong>conduct</strong>, not a code of +philosophy. And it only deals with behavior within the context of the GCC +project; for instance, harassment in private email in response to a public +discussion is covered, a social media post about politics is not.</p> + +<h3>Can I report incidents from before the adoption of the CoC?</h3> +<p>Yes. We may take no action if the issue seems to have been resolved, but it +can be helpful to have context for future discussions.</p> + +<h3>My question isn't answered here!</h3> +<p>Please also see the <a href="conduct-report.html">Reporting Guidelines</a> +and <a href="conduct-response.html">Response Guide</a>. If they don't answer +your question either, +email <a href="mailto:cond...@gcc.gnu.org";>cond...@gcc.gnu.org</a> with any +additional questions or feedback.</p> + +</body> diff --git a/htdocs/conduct-report.html b/htdocs/conduct-report.html new file mode 100644 index 00000000..13be57ce --- /dev/null +++ b/htdocs/conduct-report.html @@ -0,0 +1,122 @@ +<!DOCTYPE html> +<html lang="en"> + +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +<meta name="description" content="GCC project Code of Conduct"> +<meta name="keywords" + content="GCC, conduct"> +<title>GCC Code of Conduct Reporting Guide</title> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css";> +</head> + +<body> +<h1><a href="conduct.html">GCC Code of Conduct</a> Reporting Guide</h1> + +<h2><span style="color: red;"><strong>NOTE</strong></span><strong>: The Code +of Conduct Committee, and the formal reporting and response procedures, are not +yet fully established. The below are the currently planned procedures for when +the committee is in place.</strong></h2> + +<p>If you believe someone is violating the code of conduct we ask that you +report it to the CoC committee by +emailing <a href="mailto:cond...@gcc.gnu.org";>cond...@gcc.gnu.org</a>. <strong>All +reports will be kept confidential to the extent permitted by applicable +law.</strong> In some cases we may determine that a public statement will need +to be made. If that's the case, the identities of all reporters will remain +confidential unless they instruct us otherwise.</p> + +<p>If you are unsure whether the incident is a violation, or whether the space +where it happened is covered by this Code of Conduct, we encourage you to still +report it. We would much rather have a few extra reports where we decide to +take no action, rather than miss a report of an actual violation. We do not +look negatively on you for a report made in good faith if we find the incident +is not a violation. And knowing +about incidents that are not violations, or happen outside our spaces, can also +help us to improve the Code of Conduct or the processes surrounding it.</p> + +<p>In your report please include:</p> +<ul> + <li>Your contact info (so we can get in touch with you if we need to follow up)</li> + <li>Names (real, nicknames, or pseudonyms) of any individuals involved. If + there were other witnesses besides you, please try to include them as + well.</li> + <li>When and where the incident occurred. Please be as specific as possible.</li> + <li>Your account of what occurred. If there is a publicly available record + (e.g. a mailing list archive or a public IRC logger) please include a + link.</li> + <li>Any extra context you believe existed for the incident.</li> + <li>If you believe this incident is ongoing.</li> + <li>Any other information you believe we should have.</li> +</ul> + +<h3>What happens after you file a report?</h3> +<p>You will receive an email from the Code of Conduct Committee acknowledging +receipt. We aim to acknowledge receipt within 24 hours (and ideally +much sooner than that).</p> + +<p>The committee will then meet to review the report, and gather all available +information about the incident from the individuals involved and any electronic +records.</p> + +<p>If this is determined to be an ongoing incident or a threat to physical +safety, the committee's immediate priority will be to protect everyone +involved. This means we may delay an "official" response until we believe that +the situation has ended and that everyone is physically safe.</p> + +<p>Once the committee has a complete account of the events they will make a +decision as to how to respond. Responses may include:</p> + +<ul> + <li>Taking no further action (if we determine no violation occurred).</li> + <li>An offer to mediate between the individual(s) involved.</li> + <li>A private request or reprimand from the committee to one or more of the + individual(s) involved.</li> + <li>A public request or reprimand.</li> + <li>An imposed vacation (e.g. asking someone to "take a week off" from a + mailing list or IRC).</li> + <li>A permanent or temporary ban from some or all project spaces (mailing + lists, IRC, etc.)</li> +</ul> + +<p>We'll respond within one week to the person who filed the report with either +a resolution or an explanation of why the situation is not yet resolved.</p> + +<p>Once we've determined our final action, we'll contact the original reporter +to let them know what action (or no action) we'll be taking. We'll take into +account feedback from the reporter on the appropriateness of our response, but +we don't guarantee we'll act on it.</p> + +<p>Finally, the committee will make a report on the situation to the Steering +Committee, who may choose to make a public report of the incident.</p> + +<p>For more detail, see the <a href="conduct-response.html">Response Guide</a>. + +<h3>What if your report concerns a possible violation by a committee member?</h3> + +<p>If your report concerns a current member of the Code of Conduct committee, +you may not feel comfortable sending your report to the committee, as all +members will see the report.</p> + +<p>In that case, you can make a report directly to the current chair of the +Code of Conduct committee. Their email address is listed on the Code of Conduct +Committee page. The chair will follow the usual enforcement process with the +other members, but will exclude the member(s) that the report concerns from any +discussion or decision making.</p> + +<p>If your report concerns the chair of the committee, please send your report +directly to another member, or to a member of the Steering Committee.</p> + +<h3>Reconsideration</h3> + +<p>Any of the parties directly involved or affected can request reconsideration +of the committee's decision. To make such a request, contact a member of the +Steering Committee with your request and motivation.</p> + +<p>Text derived from +the <a href="https://www.djangoproject.com/conduct/reporting/";>Django project +Code of Conduct Reporting Guidelines</a>, used under +the <a href="https://creativecommons.org/licenses/by/3.0/";>Creative Commons +Attribution</a> license.</p> + +</body> diff --git a/htdocs/conduct-response.html b/htdocs/conduct-response.html new file mode 100644 index 00000000..6904634c --- /dev/null +++ b/htdocs/conduct-response.html @@ -0,0 +1,141 @@ +<!DOCTYPE html> +<html lang="en"> + +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +<meta name="description" content="GCC project Code of Conduct"> +<meta name="keywords" + content="GCC, conduct"> +<title>GCC Code of Conduct Response Guide</title> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css";> +</head> + +<body> +<h1><a href="conduct.html">GCC Code of Conduct</a> Response Guide</h1> + +<h2><span style="color: red;"><strong>NOTE</strong></span><strong>: The +Code of Conduct Committee, and the formal reporting and response procedures, +are not yet fully established. The below are the currently planned procedures +for when the committee is in place.</strong></h2> + +<h3>This is the process followed by the GCC Code of Conduct Committee. It's +used when we respond to an issue to make sure we're consistent and fair. It +should be considered an internal document, but we're publishing it publicly in +the interests of transparency.</h3> + +<h3>The Code of Conduct Committee</h3> + +<p>All responses to reports of conduct violations will be managed by a Code of +Conduct Committee ("the committee").</p> + +<p>The Steering Committee ("SC") will establish this committee, composed of at +least three members. One member will be designated chair of the committee and +will be responsible for all reports back to the SC. The SC will review +membership on a regular basis.</p> + +<h3>How the committee will respond to reports</h3> + +<p>When a report is sent to the committee they will immediately reply to the +report to confirm receipt. This reply should be sent within 24 hours, and +ideally much sooner than that.</p> + +<p>See the reporting guidelines for details of what reports should contain. In +addition to the report, the committee will collect all relevant data before +acting. The committee will contact all individuals involved, and refer to any +available records, to get a more complete account of events.</p> + +<p>The committee will then review the incident and determine, to the best of +their ability:</p> + +<ul> + <li>what happened</li> + <li>whether this event constitutes a code of conduct violation</li> + <li>who, if anyone, violated the code of conduct</li> + <li>whether this is an ongoing situation, and there is a threat to anyone's physical safety</li> +</ul> + +<p>This information will be collected in writing, and whenever possible the +committee's deliberations will be recorded and privately retained (i.e. IRC +transcripts, email discussions, recorded voice conversations, etc).</p> + +<p>The committee should aim to have a resolution agreed upon within one +week. In the event that a resolution can't be determined in that time, the +committee will respond to the reporter(s) with an update and projected timeline +for resolution.</p> + +<h3>Acting Unilaterally</h3> +<p>If the act is ongoing (such as someone engaging in harassment in #gcc), or +involves a threat to anyone's safety (e.g. threats of violence), any committee +member may act immediately (before reaching consensus) to end the situation. In +ongoing situations, any member may at their discretion employ any of the tools +available to the committee, including bans and blocks.</p> + +<p>If the incident involves physical danger, any member of the committee may -- +and should -- act unilaterally to protect safety. This can include contacting +law enforcement (or other local personnel) and speaking on behalf of the +project.</p> + +<p>In situations where an individual committee member acts unilaterally, they +must report their actions to the committee for review within 24 hours.</p> + +<h3>Resolutions</h3> +<p>The committee must agree on a resolution by consensus. If the committee +cannot reach consensus and deadlocks for over a week, the committee will turn +the matter over to the Steering Committee for resolution.</p> + +<p>Possible responses may include:</p> +<ul> + <li>Taking no further action (if we determine no violation occurred).</li> + <li>Offering to mediate between the individual(s) involved.</li> + <li>A private request or reprimand from the committee to one or more + individual(s) involved. In this case, a committee member will deliver that + message to the individual(s) over email, cc'ing the committee.</li> + <li>A public request or reprimand. In this case, a committee member will + deliver that message in the same venue that the violation occurred (i.e. in + IRC for an IRC violation; email for an email violation, etc.). The committee + may choose to publish this message elsewhere for posterity.</li> + <li>An imposed vacation (e.g. asking someone to "take a week off" from a + mailing list or IRC). A committee member will communicate this "vacation" to + the individual(s). They'll be asked to take this vacation voluntarily, but if + they don't agree then a temporary ban may be imposed to enforce this + vacation.</li> + <li>A permanent or temporary ban from some or all project spaces (mailing + lists, IRC, etc.). The committee will maintain records of all such bans so + that they may be reviewed in the future, extended to new project spaces, or + otherwise maintained.</li> + <li>The committee may, if it chooses, attach "strings" to a request: for + example, the committee may ask a violator to apologize in order to retain his + or her membership on a mailing list.</li> +</ul> + +<p>Once a resolution is agreed upon, but before it is enacted, the committee +will contact the original reporter and any other affected parties and explain +the proposed resolution. The committee will ask if this resolution is +acceptable, and must note feedback for the record. However, the committee is +not required to act on this feedback.</p> +<p>Finally the committee will make a report for the Steering Committee. In case +the incident or report involves a current member of the Steering Committee, the +committee will provide the report only to the other Steering Committee +members.</p> +<p>The committee will never publicly discuss the issue apart from enacting an +agreed resolution.</p> + +<h3>Transparency Reports</h3> +<p>The committee will produce periodic summaries of the reports received and +actions, if any, taken, without specific details.</p> + +<h3>Conflicts of Interest</h3> +<p>In the event of any conflict of interest a committee member must immediately +notify the other members, and recuse themselves if necessary. If a report +concerns a possible violation by a current committee member, this member is +excluded from the response process. For these cases, anyone can make a report +directly to any of the committee members, as documented in the reporting +guidelines.</p> + +<p>Text derived from +the <a href="https://www.djangoproject.com/conduct/enforcement-manual/";>Django +project Code of Conduct Enforcement Manual</a>, used under +the <a href="https://creativecommons.org/licenses/by/3.0/";>Creative Commons +Attribution</a> license.</p> + +</body> diff --git a/htdocs/conduct.html b/htdocs/conduct.html new file mode 100644 index 00000000..8fb62e86 --- /dev/null +++ b/htdocs/conduct.html @@ -0,0 +1,118 @@ +<!DOCTYPE html> +<html lang="en"> + +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> +<meta name="description" content="GCC project Code of Conduct"> +<meta name="keywords" + content="GCC, conduct"> +<title>GCC Code of Conduct</title> +<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css";> +</head> + +<body> +<h1>GCC Code of Conduct</h1> + +<p>Like the free software community as a whole, the GCC community is made up of +a mixture of professionals and volunteers from all over the world, working on +every aspect of the project - including mentorship, teaching, and connecting +people.</p> + +<p>Diversity is a huge strength, but it can also lead to communication issues +and unhappiness. To that end, we have a few ground rules that we ask people to +adhere to. This code applies equally to leaders, maintainers, and those seeking +help and guidance.</p> + +<p>This isn't an exhaustive list of things that you can or can't do. Rather, +take it in the spirit in which it's intended - a guide to make it easier to +enrich all of us, the project, and the broader communities in which we +participate.</p> + +<p>This code of conduct applies to all spaces managed by the GCC project. This +includes IRC, the mailing lists, the issue tracker, events, and any other +forums created by the project team which the community uses for +communication. In addition, violations of this code outside these spaces may +affect a person's ability to participate within them.</p> + +<ul> + <li><strong>Be friendly and patient.</strong></li> + + <li><strong>Be welcoming.</strong> We strive to be a community that welcomes + and supports people of all backgrounds and identities. This includes, but is + not limited to, members of any race, ethnicity, culture, national origin, + color, immigration status, social and economic class, educational level, sex, + sexual orientation, gender identity and expression, age, size, family status, + political belief, religion, and mental or physical ability.</li> + + <li><strong>Be considerate.</strong> Your work will be used by other people, + and you in turn will depend on the work of others. Any decision you take will + affect users and colleagues, and you should take those consequences into + account when making decisions. Remember that we're a world-wide community, so + you might not be communicating in someone else's primary language.</li> + + <li><strong>Be respectful.</strong> Not all of us will agree all the time, + but disagreement is no excuse for poor behavior and poor manners. We might + all experience some frustration now and then, but we cannot allow that + frustration to turn into a personal attack. It's important to remember that a + community where people feel uncomfortable or threatened is not a productive + one. Members of the community should be respectful when dealing with other + members as well as with people outside the community.</li> + + <li><strong>Be careful in the words that you choose.</strong> Be kind to + others. Do not insult or put down other participants. Harassment and other + exclusionary behavior aren't acceptable. This includes, but is not limited + to:</li> + + <ul> + <li>Violent threats or language directed against another person.</li> + <li>Discriminatory jokes and language.</li> + <li>Posting sexually explicit or violent material.</li> + <li>Posting (or threatening to post) other people's personally identifying information ("doxing").</li> + <li>Personal insults, especially those using racist or sexist terms.</li> + <li>Unwelcome sexual attention.</li> + <li>Advocating for, or encouraging, any of the above behavior.</li> + <li>Repeated harassment of others. In general, if someone asks you to stop, then stop.</li> + </ul> + + <li><strong>When we disagree, try to understand why.</strong> Disagreements, + both social and technical, happen all the time and the GCC community is no + exception. It is important that we resolve disagreements and differing views + constructively. A strength of free software is the varied community, people + from a wide range of backgrounds. Different people have different + perspectives on issues. Being unable to understand why someone holds a + viewpoint doesn't mean that they're wrong. Don't forget that it is human to + err and blaming each other doesn't get us anywhere. Instead, focus on helping + to resolve issues and learning from mistakes.</li> + +</ul> + +<p>See the<a href="https://www.gnu.org/philosophy/kind-communication.en.html";> +GNU Kind Communications Guidelines</a> for more guidance on constructive +interactions.</p> + +<p>If you believe someone is violating the code of conduct, we ask that you +report it by +emailing <a href="mailto:cond...@gcc.gnu.org";>cond...@gcc.gnu.org</a>. For +more details please see our <a href="conduct-report.html">Reporting +Guidelines</a>.</p> + +<h2>Code of Conduct Committee</h2> + +<p>The Code of Conduct Committee, and the formal reporting and response +procedures, are not yet fully established. For the time +being, <a href="mailto:cond...@gcc.gnu.org";>cond...@gcc.gnu.org</a> will go to +some members of the Steering Committee. If you are interested in serving +on the CoC committee, or would like to suggest someone who you think would be a +good candidate, please +email <a href="mailto:cond...@gcc.gnu.org";>cond...@gcc.gnu.org</a>.</p> + +<h2>Questions?</h2> + +<p>If you have questions, please see <a href="conduct-faq.html">the FAQ</a>. If +that doesn't answer your questions, feel free +to <a href="mailto:cond...@gcc.gnu.org";>contact us</a>.</p> + +<p>Text derived from the <a href="https://www.djangoproject.com/conduct/";>Django +project Code of Conduct</a>, used under +the <a href="https://creativecommons.org/licenses/by/3.0/";>Creative Commons +Attribution</a> license.</p> diff --git a/htdocs/index.html b/htdocs/index.html index decd4ff6..0752eb9c 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -55,6 +55,9 @@ mission statement</a>.</p> <h2 id="news">News</h2> <dl> +<dt><span><a href="conduct.html">GCC Code of Conduct</a> adopted</span> + <span class="date">[2023-06-16]</span></dt> + <dt><span><a href="https://gcc.gnu.org/wiki/cauldron2022";>GNU Tools Cauldron 2022</a></span> <span class="date">[2022-09-02]</span></dt> <dd>Prague, Czech Republic and online, September 16-18 2022</dd> diff --git a/htdocs/lists.html b/htdocs/lists.html index b50e9ac3..03e4a2a2 100644 --- a/htdocs/lists.html +++ b/htdocs/lists.html @@ -201,6 +201,8 @@ web-based e-mail account.</p> <p>are acceptable, although they are redundant; unless explicitly stated, it's assumed that no-one on these lists means to speak for their company.</p> +<p>The <a href="conduct.html">GCC Code of Conduct</a> applies to conversations +on the mailing lists.</p> <h2 id="subscribe">Subscribing/unsubscribing</h2> base-commit: a459257a46fdaa70096d06d84322805dba830bcd -- 2.39.3
