Skip to content

Commit fbfe5d5

Browse files
committed
code of conduct and expectations section in readme
1 parent 013c217 commit fbfe5d5

File tree

2 files changed

+145
-0
lines changed

2 files changed

+145
-0
lines changed

CODE_OF_CONDUCT.md

+135
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,135 @@
1+
<!--
2+
SPDX-FileCopyrightText: 2014 Coraline Ada Ehmke
3+
SPDX-FileCopyrightText: 2019 Kattni Rembor for Adafruit Industries
4+
SPDX-License-Identifier: CC-BY-4.0
5+
-->
6+
7+
# Adafruit Community Code of Conduct
8+
9+
## Our Pledge
10+
11+
In the interest of fostering an open and welcoming environment, we as
12+
contributors and leaders pledge to making participation in our project and
13+
our community a harassment-free experience for everyone, regardless of age, body
14+
size, disability, ethnicity, gender identity and expression, level or type of
15+
experience, education, socio-economic status, nationality, personal appearance,
16+
race, religion, or sexual identity and orientation.
17+
18+
## Our Standards
19+
20+
We are committed to providing a friendly, safe and welcoming environment for
21+
all.
22+
23+
Examples of behavior that contributes to creating a positive environment
24+
include:
25+
26+
* Be kind and courteous to others
27+
* Using welcoming and inclusive language
28+
* Being respectful of differing viewpoints and experiences
29+
* Collaborating with other community members
30+
* Gracefully accepting constructive criticism
31+
* Focusing on what is best for the community
32+
* Showing empathy towards other community members
33+
34+
Examples of unacceptable behavior by participants include:
35+
36+
* The use of sexualized language or imagery and sexual attention or advances
37+
* The use of inappropriate images, including in a community member's avatar
38+
* The use of inappropriate language, including in a community member's nickname
39+
* Any spamming, flaming, baiting or other attention-stealing behavior
40+
* Excessive or unwelcome helping; answering outside the scope of the question
41+
asked
42+
* Trolling, insulting/derogatory comments, and personal or political attacks
43+
* Promoting or spreading disinformation, lies, or conspiracy theories against
44+
a person, group, organisation, project, or community
45+
* Public or private harassment
46+
* Publishing others' private information, such as a physical or electronic
47+
address, without explicit permission
48+
* Other conduct which could reasonably be considered inappropriate
49+
50+
The goal of the standards and moderation guidelines outlined here is to build
51+
and maintain a respectful community. We ask that you don’t just aim to be
52+
"technically unimpeachable", but rather try to be your best self.
53+
54+
We value many things beyond technical expertise, including collaboration and
55+
supporting others within our community. Providing a positive experience for
56+
other community members can have a much more significant impact than simply
57+
providing the correct answer.
58+
59+
## Our Responsibilities
60+
61+
Project leaders are responsible for clarifying the standards of acceptable
62+
behavior and are expected to take appropriate and fair corrective action in
63+
response to any instances of unacceptable behavior.
64+
65+
Project leaders have the right and responsibility to remove, edit, or
66+
reject messages, comments, commits, code, issues, and other contributions
67+
that are not aligned to this Code of Conduct, or to ban temporarily or
68+
permanently any community member for other behaviors that they deem
69+
inappropriate, threatening, offensive, or harmful.
70+
71+
## Moderation
72+
73+
Instances of behaviors that violate the Adafruit Community Code of Conduct
74+
may be reported by any member of the community. Community members are
75+
encouraged to report these situations, including situations they witness
76+
involving other community members.
77+
78+
You may report in the following ways:
79+
80+
In any situation, you may send an email to <[email protected]>.
81+
82+
On the Adafruit Discord, you may send an open message from any channel
83+
to all Community Moderators by tagging @community moderators. You may
84+
also send an open message from any channel, or a direct message to
85+
@kattni#1507, @tannewt#4653, @Dan Halbert#1614, @cater#2442,
86+
@sommersoft#0222, @Mr. Certainly#0472 or @Andon#8175.
87+
88+
Email and direct message reports will be kept confidential.
89+
90+
In situations on Discord where the issue is particularly egregious, possibly
91+
illegal, requires immediate action, or violates the Discord terms of service,
92+
you should also report the message directly to Discord.
93+
94+
These are the steps for upholding our community’s standards of conduct.
95+
96+
1. Any member of the community may report any situation that violates the
97+
Adafruit Community Code of Conduct. All reports will be reviewed and
98+
investigated.
99+
2. If the behavior is an egregious violation, the community member who
100+
committed the violation may be banned immediately, without warning.
101+
3. Otherwise, moderators will first respond to such behavior with a warning.
102+
4. Moderators follow a soft "three strikes" policy - the community member may
103+
be given another chance, if they are receptive to the warning and change their
104+
behavior.
105+
5. If the community member is unreceptive or unreasonable when warned by a
106+
moderator, or the warning goes unheeded, they may be banned for a first or
107+
second offense. Repeated offenses will result in the community member being
108+
banned.
109+
110+
## Scope
111+
112+
This Code of Conduct and the enforcement policies listed above apply to all
113+
Adafruit Community venues. This includes but is not limited to any community
114+
spaces (both public and private), the entire Adafruit Discord server, and
115+
Adafruit GitHub repositories. Examples of Adafruit Community spaces include
116+
but are not limited to meet-ups, audio chats on the Adafruit Discord, or
117+
interaction at a conference.
118+
119+
This Code of Conduct applies both within project spaces and in public spaces
120+
when an individual is representing the project or its community. As a community
121+
member, you are representing our community, and are expected to behave
122+
accordingly.
123+
124+
## Attribution
125+
126+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
127+
version 1.4, available at
128+
<https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>,
129+
and the [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html).
130+
131+
For other projects adopting the Adafruit Community Code of
132+
Conduct, please contact the maintainers of those projects for enforcement.
133+
If you wish to use this code of conduct for your own project, consider
134+
explicitly mentioning your moderation policy or making a copy with your
135+
own moderation policy so as to avoid confusion.

README.md

+10
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,16 @@ also do `git submodule update`.
3030
To update the libraries run `update-submodules.sh`. The script will fetch the
3131
latest code and update to the newest tag (not master).
3232

33+
## Expectations for Library Inclusion
34+
You're interested in having your library included in the Community Bundle? Great! Here are some things to keep in mind:
35+
36+
* The subject and content of your library has to be compatible with the [Adafruit Community Code of Conduct](CODE_OF_CONDUCT.md)
37+
* Tagged release of the library must be compatible with [circuitpython-build-tools](https://github.com/adafruit/circuitpython-build-tools). The best way to ensure this is to use Github Actions with files like those produced by our [Cookie Cutter](https://github.com/adafruit/cookiecutter-adafruit-circuitpython/)
38+
* If your library has a problematic release that impacts Community Bundle releases, you will do your best to resolve it in a timely manner
39+
* If future changes to circuitpython-build-tools impact your library, you will do your best to resolve it in a timely manner (we try to keep breaking changes to a minimum, but they do happen!)
40+
41+
If a particular library is causing problems for distribution in the Community Bundle we may temporarily drop it or hold it at an old revision, so that we can continue making Community Bundle releases.
42+
3343
## Adding a library
3444
Determine the best location within `libraries` for the new library and then run:
3545

0 commit comments

Comments
 (0)