From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2122) id 83159385B522; Tue, 20 Jun 2023 16:23:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 83159385B522 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1687278224; bh=4JEbvPOOkUfJOKTlrJAVQNwZeSTWcJZHv44GuNPCtKw=; h=To:Subject:Date:From:From; b=lK0Zp1Twx9cs3dYRc96TXXEcLy6A5FcwwcHCTJH0TwRZEQJrq+j7ExhUiMbwh3gqv zyryG96kn/+9mlWkj+f95uzWgu5iMsuxt/Xmfb8RegQVoc0i6WE4oZSvL2yoJPoDFI Eq5kTWfGQx4EeXfHJ3/Lkj/XjUtERYeB2QSLpCWI= To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 36a9a45a1f5bc4e49d8a15c60b425921584b1fc1 X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: e48038c3f56ea858222f79162c74e858886f572d X-Git-Newrev: 36a9a45a1f5bc4e49d8a15c60b425921584b1fc1 Message-Id: <20230620162344.83159385B522@sourceware.org> Date: Tue, 20 Jun 2023 16:23:43 +0000 (GMT) From: Jason Merrill List-Id: This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 36a9a45a1f5bc4e49d8a15c60b425921584b1fc1 (commit) from e48038c3f56ea858222f79162c74e858886f572d (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 36a9a45a1f5bc4e49d8a15c60b425921584b1fc1 Author: Jason Merrill Date: Thu Jun 15 09:14:18 2023 -0400 Add GCC Code of Conduct diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index 3744a28f..c068560f 100644 --- a/htdocs/bugs/index.html +++ b/htdocs/bugs/index.html @@ -123,6 +123,9 @@ three of which can be obtained from the output of gcc -v:

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.

+ +

Violations of the Code of Conduct.

Where to post it

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 @@ + + + + + + + +GCC Code of Conduct FAQ + + + + +

GCC Code of Conduct FAQ

+ +

Why adopt a Code of Conduct?

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.

+ +

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.

+ +

Why not just refer to the GNU Kind Communication Guidelines?

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.

+ +

Shouldn't people try to work problems out between themselves first?

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.

+ +

What about the rights of the reportee?

The CoC committee will get their perspective, and any other available +information, before taking any action.

+ +

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 Linux Kernel +CoC reports for an example.

+ +

Is this going to be used to drive out people with "wrong" opinions?

No, this is a code of conduct, 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.

+ +

Can I report incidents from before the adoption of the CoC?

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.

+ +

My question isn't answered here!

Please also see the Reporting Guidelines +and Response Guide. If they don't answer +your question either, +email conduct@gcc.gnu.org with any +additional questions or feedback.

+ + 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 @@ + + + + + + + +GCC Code of Conduct Reporting Guide + + + + +

GCC Code of Conduct Reporting Guide

+ +

NOTE: 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.

+ +

If you believe someone is violating the code of conduct we ask that you +report it to the CoC committee by +emailing conduct@gcc.gnu.org. All +reports will be kept confidential to the extent permitted by applicable +law. 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.

+ +

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.

+ +

In your report please include:

Your contact info (so we can get in touch with you if we need to follow up)
Names (real, nicknames, or pseudonyms) of any individuals involved. If + there were other witnesses besides you, please try to include them as + well.
When and where the incident occurred. Please be as specific as possible.
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.
Any extra context you believe existed for the incident.
If you believe this incident is ongoing.
Any other information you believe we should have.

+ +

What happens after you file a report?

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).

+ +

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.

+ +

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.

+ +

Once the committee has a complete account of the events they will make a +decision as to how to respond. Responses may include:

+ +

Taking no further action (if we determine no violation occurred).
An offer to mediate between the individual(s) involved.
A private request or reprimand from the committee to one or more of the + individual(s) involved.
A public request or reprimand.
An imposed vacation (e.g. asking someone to "take a week off" from a + mailing list or IRC).
A permanent or temporary ban from some or all project spaces (mailing + lists, IRC, etc.)

+ +

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.

+ +

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.

+ +

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.

+ +

For more detail, see the Response Guide. + +

What if your report concerns a possible violation by a committee member?

+ +

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.

+ +

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.

+ +

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.

+ +

Reconsideration

+ +

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.

+ +

Text derived from +the Django project +Code of Conduct Reporting Guidelines, used under +the Creative Commons +Attribution license.

+ + 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 @@ + + + + + + + +GCC Code of Conduct Response Guide + + + + +

GCC Code of Conduct Response Guide

+ +

NOTE: 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.

+ +

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.

+ +

The Code of Conduct Committee

+ +

All responses to reports of conduct violations will be managed by a Code of +Conduct Committee ("the committee").

+ +

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.

+ +

How the committee will respond to reports

+ +

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.

+ +

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.

+ +

The committee will then review the incident and determine, to the best of +their ability:

+ +

what happened
whether this event constitutes a code of conduct violation
who, if anyone, violated the code of conduct
whether this is an ongoing situation, and there is a threat to anyone's physical safety

+ +

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).

+ +

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.

+ +

Acting Unilaterally

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.

+ +

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.

+ +

In situations where an individual committee member acts unilaterally, they +must report their actions to the committee for review within 24 hours.

+ +

Resolutions

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.

+ +

Possible responses may include:

Taking no further action (if we determine no violation occurred).
Offering to mediate between the individual(s) involved.
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.
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.
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.
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.
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.

+ +

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.

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.

The committee will never publicly discuss the issue apart from enacting an +agreed resolution.

+ +

Transparency Reports

The committee will produce periodic summaries of the reports received and +actions, if any, taken, without specific details.

+ +

Conflicts of Interest

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.

+ +

Text derived from +the Django +project Code of Conduct Enforcement Manual, used under +the Creative Commons +Attribution license.

+ + 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 @@ + + + + + + + +GCC Code of Conduct + + + + +

GCC Code of Conduct

+ +

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.

+ +

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.

+ +

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.

+ +

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.

+ +

Be friendly and patient.
Be welcoming. 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.
Be considerate. 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.
Be respectful. 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.
Be careful in the words that you choose. 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:

Violent threats or language directed against another person.
Discriminatory jokes and language.
Posting sexually explicit or violent material.
Posting (or threatening to post) other people's personally identifying information ("doxing").
Personal insults, especially those using racist or sexist terms.
Unwelcome sexual attention.
Advocating for, or encouraging, any of the above behavior.
Repeated harassment of others. In general, if someone asks you to stop, then stop.

When we disagree, try to understand why. 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.

+ +

See the +GNU Kind Communications Guidelines for more guidance on constructive +interactions.

+ +

If you believe someone is violating the code of conduct, we ask that you +report it by +emailing conduct@gcc.gnu.org. For +more details please see our Reporting +Guidelines.

+ +

Code of Conduct Committee

+ +

The Code of Conduct Committee, and the formal reporting and response +procedures, are not yet fully established. For the time +being, conduct@gcc.gnu.org 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 conduct@gcc.gnu.org.

+ +

Questions?

+ +

If you have questions, please see the FAQ. If +that doesn't answer your questions, feel free +to contact us.

+ +

Text derived from the Django +project Code of Conduct, used under +the Creative Commons +Attribution license.

diff --git a/htdocs/index.html b/htdocs/index.html index 9e8e96ee..fa2fa756 100644 --- a/htdocs/index.html +++ b/htdocs/index.html @@ -55,6 +55,9 @@ mission statement.

News

GCC Code of Conduct adopted + [2023-06-16]
GCC 11.4 released [2023-05-29]