File: CODE_OF_CONDUCT.md

package info (click to toggle)
ruby-rspec-rails 8.0.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,820 kB
  • sloc: ruby: 10,902; sh: 199; makefile: 6
file content (183 lines) | stat: -rw-r--r-- 9,296 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
# Contributor Code of Conduct

For the purpose of building a welcoming, harassment-free community that
values contributions from anyone, the RSpec project has adopted the
following code of conduct. All contributors and participants (including
maintainers!) are expected to abide by its terms.

As contributors and maintainers of this project, we pledge to make our community
welcoming, safe, and equitable for all.

We are committed to fostering an environment that respects and promotes the
dignity, rights, and contributions of all individuals, regardless of
characteristics including race, ethnicity, caste, color, age, physical
characteristics, neurodiversity, disability, sex or gender, gender identity
or expression, sexual orientation, language, philosophy or religion, national
or social origin, socio-economic position, level of education, or other status.
The same privileges of participation are extended to everyone who participates
in good faith and in accordance with this Covenant.

By adopting this Code of Conduct, project maintainers commit themselves to
fairly and consistently applying these principles to every aspect of managing
this project. Project maintainers who do not follow or enforce the Code of
Conduct may be permanently removed from the project team.

## Encouraged Behaviors

While acknowledging differences in social norms, we all strive to meet our
community's expectations for positive behavior. We also understand that our
words and actions may be interpreted differently than we intend based on
culture, background, or native language.

With these considerations in mind, we agree to behave mindfully toward each
other and act in ways that center our shared values, including:

1. Respecting the **purpose of our community**, our activities,
   and our ways of gathering.
2. Engaging **kindly and honestly** with others.
3. Respecting **different viewpoints** and experiences.
4. **Taking responsibility** for our actions and contributions.
5. Gracefully giving and accepting **constructive feedback**.
6. Committing to **repairing harm** when it occurs.
7. Behaving in other ways that promote and sustain the
   **well-being of our community**.

## Restricted Behaviors

We agree to restrict the following behaviors in our community. Instances,
threats, and promotion of these behaviors are violations of this
Code of Conduct.

1. **Harassment.** Violating explicitly expressed boundaries or engaging in
   unnecessary personal attention after any clear request to stop.
2. **Character attacks.** Making insulting, demeaning, or pejorative comments
   directed at a community member or group of people.
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
   behavior on the basis of immutable identities or traits.
4. **Sexualization.** Behaving in a way that would generally be considered
   inappropriately intimate in the context or purpose of the community.
5. **Violating confidentiality**. Sharing or acting on someone's personal or
   private information without their permission.
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm
   toward any person or group.
7. Behaving in other ways that **threaten the well-being** of our community.

### Other Restrictions

1. **Misleading identity.** Impersonating someone else for any reason, or
   pretending to be someone else to evade enforcement actions.
2. **Failing to credit sources.** Not properly crediting the sources of content
   you contribute, including but not limited to the use of LLMs.
3. **Promotional materials**. Sharing marketing or other commercial content in
   a way that is outside the norms of the community.
4. **Irresponsible communication.** Failing to responsibly present content which
   includes, links or describes any other restricted behaviors.

## Reporting an Issue

Tensions can occur between community members even when they are trying their
best to collaborate. Not every conflict represents a code of conduct violation,
and this Code of Conduct reinforces encouraged behaviors and norms that can
help avoid conflicts and minimize harm.

When an incident does occur, it is important to report it promptly.

To report a possible violation contact one of the project maintainers listed at
https://rspec.info/about/. All complaints will be reviewed and investigated
and will result in a response that is deemed necessary and appropriate to the
circumstances.

Maintainers take reports of violations seriously and will make every effort to
respond in a timely manner. They will investigate all reports of code of conduct
violations, reviewing messages, logs, and recordings, or interviewing witnesses
and other participants. Maintainers will keep investigation and enforcement
actions as transparent as possible while prioritizing safety and
confidentiality. In order to honor these values, enforcement actions are carried
out in private with the involved parties, but communicating to the whole
community may be part of a mutually agreed upon resolution.

## Addressing and Repairing Harm

Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.

If an investigation that this Code of Conduct has been violated, the following
enforcement ladder may be used to determine how best to repair harm, based on
the incident's impact on the individuals involved and the community as a whole.
Depending on the severity of a violation, lower rungs on the ladder may be
skipped.

1) Warning
   1) Event: A violation involving a single incident or series of incidents.
   2) Consequence: A private, written warning.
   3) Repair: Examples of repair include a private written apology,
      acknowledgement of responsibility, and seeking clarification on
      expectations.

2) Temporarily Limited Activities
   1) Event: A repeated incidence of a violation that previously resulted in a
      warning, or the first incidence of a more serious violation.
   2) Consequence: A private, written warning with a time-limited cooldown
      period designed to underscore the seriousness of the situation and give
      the community members involved time to process the incident. The cooldown
      period may be limited to particular communication channels or interactions
      with particular community members.
   3) Repair: Examples of repair may include making an apology, using the
      cooldown period to reflect on actions and impact, and being thoughtful
      about re-entering community spaces after the period is over.

3) Temporary Suspension
   1) Event: A pattern of repeated violation which have been issued warnings,
      or a single serious violation.
   2) Consequence: A private written warning with conditions for return from
      suspension. In general, temporary suspensions give the person being
      suspended time to reflect upon their behavior and possible corrective
      actions.
   3) Repair: Examples of repair include respecting the spirit of the
      suspension, meeting the specified conditions for return, and being
      thoughtful about how to reintegrate with the community when the suspension
      is lifted.

4) Permanent Ban
   1) Event: A pattern of repeated code of conduct violations that other steps
      on the ladder have failed to resolve, or a violation so serious that it
      is determined there is no way to keep the community safe with this person
      as a member.
   2) Consequence: Access to all community spaces, tools, and communication
      channels is removed. In general, permanent bans should be rarely used,
      should have strong reasoning behind them, and should only be resorted to
      if working through other remedies has failed to change the behavior.
   3) Repair: There is no possible repair in cases of this severity.

This enforcement ladder is intended as a guideline. It does not limit the
ability of maintainers to use their discretion and judgment, in keeping
with the best interests of our community.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public or other
spaces. Examples of representing our community include using an official email
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 3.0, available at
[https://www.contributor-covenant.org/version/3/0/][version]

Contributor Covenant is stewarded by the Organization for Ethical Source and
licensed under CC BY-SA 4.0. To view a copy of this license, visit
[https://creativecommons.org/licenses/by-sa/4.0/][cc-by-sa]

For answers to common questions about Contributor Covenant, see their
[FAQ][faq].

[cc-by-sa]: https://creativecommons.org/licenses/by-sa/4.0/
[homepage]: https://contributor-covenant.org
[faq]: https://www.contributor-covenant.org/faq
[version]: https://www.contributor-covenant.org/version/3/0/