Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit d4f40c7

Browse filesBrowse files
committed
Adding guidelines for reporting violations of code of conduct
1 parent 8e88bd9 commit d4f40c7
Copy full SHA for d4f40c7

File tree

Expand file treeCollapse file tree

4 files changed

+179
-0
lines changed
Filter options
Expand file treeCollapse file tree

4 files changed

+179
-0
lines changed
+66Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
Enforcement team
2+
================
3+
4+
The role of the enforcement team is to make sure the :doc:`Code of Conduct </contributing/code_of_conduct/index>`
5+
is respected. If you think there is or has been a violation to the code of conduct
6+
please read the :doc:`reporting guidelines </contributing/code_of_conduct/reporting_guidelines>`
7+
and contact any person in the enforcement team.
8+
9+
Members
10+
-------
11+
12+
Lukas Kahwe Smith
13+
`````````````````
14+
.. image:: https://avatars3.githubusercontent.com/u/300279?s=400&v=4
15+
:height: 150px
16+
:width: 150px
17+
:alt: Likas Kahwe Smith
18+
:class: pull-right
19+
20+
Lukas is part of symfony core team and working for Liip. Lorem ipsum dolor sit amet,
21+
consectetur adipiscing elit. Proin enim nibh, susciit sed rhoncus quis, blandit
22+
quis sapien. Ut congue pharetra rhoncus.
23+
24+
| **Email:** smith@pooteeweet.org
25+
| **Twitter:** @lsmith
26+
27+
Lukas Kahwe Smith
28+
`````````````````
29+
.. image:: https://avatars3.githubusercontent.com/u/300279?s=400&v=4
30+
:height: 150px
31+
:width: 150px
32+
:alt: Likas Kahwe Smith
33+
:class: pull-right
34+
35+
Lukas is part of symfony core team and working for Liip. Lorem ipsum dolor sit amet,
36+
consectetur adipiscing elit. Proin enim nibh, suscipit sed rhoncus quis, blandit
37+
quis sapien. Ut congue pharetra rhoncus.
38+
39+
| **Email:** smith@pooteeweet.org
40+
| **Twitter:** @lsmith
41+
42+
Lukas Kahwe Smith
43+
`````````````````
44+
.. image:: https://avatars3.githubusercontent.com/u/300279?s=400&v=4
45+
:height: 150px
46+
:width: 150px
47+
:alt: Likas Kahwe Smith
48+
:class: pull-right
49+
50+
Lukas is part of symfony core team and working for Liip. Lorem ipsum dolor sit amet,
51+
consectetur adipiscing elit. Proin enim nibh, suscipit sed rhoncus quis, blandit
52+
quis sapien. Ut congue pharetra rhoncus.
53+
54+
| **Email:** smith@pooteeweet.org
55+
| **Twitter:** @lsmith
56+
57+
About the Enforcement Team
58+
--------------------------
59+
60+
The :doc:`Symfony core team </contributing/code/core_team>` appoints enforcement
61+
team with candidates they see fit. The enforcement team will consists of at least
62+
be 3 persons. The team should be representing as many demographics as possible,
63+
ideally from different employers and not in a private partnership with Symfony
64+
and/or SensioLabs.
65+
66+
+14Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
Code of Conduct
2+
===============
3+
4+
This page will have our code of conduct. At the moment it is a place holder for
5+
https://github.com/symfony/symfony/pull/24896
6+
7+
Related documents
8+
-----------------
9+
10+
.. toctree::
11+
:maxdepth: 1
12+
13+
reporting_guidelines
14+
enforcement_team
+98Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
Reporting Guidelines
2+
====================
3+
4+
If you believe someone is violating the code of conduct we ask that you report
5+
it to the :doc:`enforcement team </contributing/code_of_conduct/enforcement_team>`
6+
by emailing, twitter, in person or any way you see fit.
7+
8+
**All reports will be kept confidential.** In some cases we may determine that
9+
a public statement will need to be made. If that's the case, the identities of
10+
all victims, reporters, and the accused will remain confidential unless those
11+
individuals instruct us otherwise.
12+
13+
If you believe anyone is in physical danger, please notify appropriate emergency
14+
services first by calling the relevant local authorities. If you are unsure what
15+
service or agency is appropriate to contact, include this in your report and we
16+
will attempt to notify them.
17+
18+
In your report please include:
19+
20+
* Your contact info for follow-up contact.
21+
* Names (legal, nicknames, or pseudonyms) of any individuals involved.
22+
* If there were other witnesses besides you, please try to include them as well.
23+
* When and where the incident occurred. Please be as specific as possible.
24+
* Your account of what occurred.
25+
* If there is a publicly available record (e.g. a mailing list archive or a
26+
public IRC or Slack log), please include a link.
27+
* Any extra context you believe existed for the incident.
28+
* If you believe this incident is ongoing.
29+
* Any other information you believe we should have.
30+
31+
What happens after you file a report?
32+
-------------------------------------
33+
34+
You will receive a reply from the :doc:`enforcement team </contributing/code_of_conduct/enforcement_team>`
35+
acknowledging receipt as soon as possible, but within 24 hours.
36+
37+
The team will immediately meet to review the incident and determine:
38+
39+
* What happened.
40+
* Whether this event constitutes a code of conduct violation.
41+
* What kind of response is appropriate.
42+
43+
If this is determined to be an ongoing incident or a threat to physical safety,
44+
the team's immediate priority will be to protect everyone involved. This means
45+
we may delay an "official" response until we believe that the situation has ended
46+
and that everyone is physically safe.
47+
48+
Once the team has a complete account of the events, they will make a decision as
49+
to how to respond. Responses may include:
50+
51+
* Nothing (if we determine no code of conduct violation occurred).
52+
* A private reprimand from the Code of Conduct response team to the individual(s)
53+
involved.
54+
* A public reprimand.
55+
* An imposed vacation (i.e. asking someone to "take a week off" from a mailing
56+
list or Slack).
57+
* A permanent or temporary ban from some or all Symfony conference/community
58+
spaces (events, meetings, mailing lists, IRC, Slack, etc.)
59+
* A request to engage in mediation and/or an accountability plan.
60+
* On a case by case basis, the enforcement team might share information an incidents
61+
with employers or other 3rd parties in order to fulfill their mandate.
62+
63+
We'll respond within one week to the person who filed the report with either a
64+
resolution or an explanation of why the situation is not yet resolved.
65+
66+
Once we've determined our final action, we'll contact the original reporter to
67+
let them know what action (if any) we'll be taking. We'll take into account feedback
68+
from the reporter on the appropriateness of our response, but our response will be
69+
determined by what will be best for community safety.
70+
71+
The enforcement team keeps a private record of all incidents. By default all reports
72+
are shared with the entire enforcement team unless the reporter specifically asks
73+
to exclude specific enforcement team members, in which case these enforcement team
74+
members will not be included in any communication on the incidents as well as records
75+
created related to the incidents.
76+
77+
Enforcement team members are expected to inform the enforcement team and the reporters
78+
in case of conflicts on interest and recuse themselves if this is deemed a problem.
79+
80+
Appealing the response
81+
----------------------
82+
83+
Only permanent resolutions (such as bans) may be appealed. To appeal a decision
84+
of the working group, contact the :doc:`enforcement team </contributing/code_of_conduct/enforcement_team>`
85+
with your appeal and they will review the case.
86+
87+
Document origin
88+
---------------
89+
90+
Reporting Guidelines derived from those of the `Stumptown Syndicate`_ and the
91+
`Django Software Foundation`_.
92+
93+
Adopted by `Symfony`_ organizers on 21 February 2018.
94+
95+
96+
.. _`Stumptown Syndicate`: http://stumptownsyndicate.org/code-of-conduct/reporting-guidelines/
97+
.. _`Django Software Foundation`: https://www.djangoproject.com/conduct/reporting/
98+
.. _`Symfony`: https://symfony.com

‎contributing/index.rst

Copy file name to clipboardExpand all lines: contributing/index.rst
+1Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,5 +7,6 @@ Contributing
77
code/index
88
documentation/index
99
community/index
10+
code_of_conduct/index
1011

1112
.. include:: /contributing/map.rst.inc

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.