mirror of
https://github.com/symfony/symfony-docs.git
synced 2026-03-24 00:32:14 +01:00
99 lines
4.6 KiB
ReStructuredText
99 lines
4.6 KiB
ReStructuredText
Reporting Guidelines
|
|
====================
|
|
|
|
If you believe someone is violating the Code of Conduct we ask that you report
|
|
it to the :doc:`CARE team </contributing/code_of_conduct/care_team>`
|
|
by emailing, Twitter, in person or any way you see fit.
|
|
|
|
**All reports will be kept confidential.** The privacy of everyone included in
|
|
the report is of our highest concern. Second to privacy there is transparency.
|
|
After every report we will determine if a public statement should be made. If
|
|
that's the case, the identities of all victims, reporters, and the accused will
|
|
remain confidential unless those individuals instruct us otherwise. The details
|
|
of the incident may also be generalized.
|
|
|
|
If you believe anyone is in physical danger or doing something that is against
|
|
the law, please notify appropriate emergency services first by calling the relevant
|
|
local authorities. If you are unsure what service or agency is appropriate to
|
|
contact, include this in your report and we will attempt to notify them.
|
|
|
|
In your report please include:
|
|
|
|
* Your contact info for follow-up contact.
|
|
* Names (legal, 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 description of what occurred.
|
|
* If there is a publicly available record (e.g. a mailing list archive or a
|
|
public IRC or Slack log), please include a link and a screenshot.
|
|
* 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 a reply from the :doc:`CARE team </contributing/code_of_conduct/care_team>`
|
|
acknowledging receipt as soon as possible, but within 24 hours.
|
|
|
|
The team member receiving the report will immediately contact all or some other
|
|
CARE team members to review the incident and determine:
|
|
|
|
* What happened.
|
|
* Whether this event constitutes a Code of Conduct violation.
|
|
* What kind of response is appropriate.
|
|
|
|
If this is determined to be an ongoing incident or a threat to physical safety,
|
|
the team'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 team has a complete account of the events, they will make a decision as
|
|
to how to respond. Responses may include:
|
|
|
|
* Nothing (if we determine no Code of Conduct violation occurred).
|
|
* A private reprimand from the Code of Conduct response team to the individual(s)
|
|
involved.
|
|
* An imposed vacation (i.e. asking someone to "take a week off" from a mailing
|
|
list or Slack).
|
|
* A permanent or temporary ban from some or all Symfony conference/community
|
|
spaces (events, meetings, mailing lists, IRC, Slack, etc.)
|
|
* A request to engage in mediation and/or an accountability plan.
|
|
* On a case by case basis, other actions may be possible but will usually be
|
|
coordinated with the core team and the Symfony company.
|
|
|
|
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 actions, we'll contact the original reporter to
|
|
let them know what action (if any) we'll be taking. We'll take into account feedback
|
|
from the reporter on the appropriateness of our response, but our response will be
|
|
determined by what will be best for community safety.
|
|
|
|
The CARE team keeps a private record of all incidents. By default, all reports
|
|
are shared with the entire CARE team unless the reporter specifically asks
|
|
to exclude specific CARE team members, in which case these CARE team
|
|
members will not be included in any communication on the incidents as well as records
|
|
created related to the incidents.
|
|
|
|
CARE team members are expected to inform the CARE team and the reporters
|
|
in case of a conflict of interest, and recuse themselves if this is deemed to be a problem.
|
|
|
|
Appealing the response
|
|
----------------------
|
|
|
|
Only permanent resolutions (such as bans) may be appealed. To appeal a decision
|
|
of the working group, contact the :doc:`CARE team </contributing/code_of_conduct/care_team>`
|
|
with your appeal and they will review the case.
|
|
|
|
Document origin
|
|
---------------
|
|
|
|
Reporting Guidelines derived from those of the `Stumptown Syndicate`_ and the
|
|
`Django Software Foundation`_.
|
|
|
|
Adopted by `Symfony`_ organizers on 21 February 2018.
|
|
|
|
.. _`Stumptown Syndicate`: https://github.com/stumpsyn/policies/blob/master/reporting_guidelines.md/
|
|
.. _`Django Software Foundation`: https://www.djangoproject.com/conduct/reporting/
|
|
.. _`Symfony`: https://symfony.com
|