Skip to content

Commit be5341b

Browse files
authored
Merge pull request #131 from poldracklab/oesteban-patch-1
DOC: Transfer CoC from NiBabel
2 parents 7bdaef1 + 002f4c0 commit be5341b

File tree

1 file changed

+108
-0
lines changed

1 file changed

+108
-0
lines changed

CODE_OF_CONDUCT.md

Lines changed: 108 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,108 @@
1+
# Community Guidelines
2+
3+
Nibabel and *NiTransforms* (a *NiBabel* feature-repo) are [NIPY](https://nipy.org) projects,
4+
and we strive to adhere to the
5+
[NIPY code of conduct](https://nipy.org/conduct.html), reproduced below.
6+
7+
The NIPY community is a community of practice devoted to the use of the Python programming language
8+
in the analysis of neuroimaging data. The following code of conduct is a guideline for our behavior
9+
as we participate in this community.
10+
11+
It is based on, and heavily inspired by a reading of the Python community code of conduct, the
12+
Apache foundation code of conduct, the Debian code of conduct, and the Ten Principles of Burning
13+
Man.
14+
15+
## The code of conduct for the NIPY community
16+
17+
The Neuroimaging in Python (NIPY) community is made up of members with a diverse set of skills,
18+
personalities, background, and experiences. We welcome these differences because they are the
19+
source of diverse ideas, solutions and decisions about our work. Decisions we make affect users,
20+
colleagues, and through scientific results, the general public. We take these consequences
21+
seriously when making decisions. When you are working with members of the community, we ask
22+
you to follow these guidelines, which help steer our interactions and help keep NIPY a positive,
23+
successful, and growing community.
24+
25+
### A member of the NIPY community is:
26+
27+
#### Open
28+
29+
Members of the community are open to collaboration. Be it on the reuse of data, on the
30+
implementation of methods, on finding technical solutions, establishing best practices, and
31+
otherwise. We are accepting of all who wish to take part in our activities, fostering an
32+
environment where anyone can participate and everyone can make a difference.
33+
34+
#### Collaborative
35+
36+
Our work will be used by other people, and in turn we will depend on the work of others. When we
37+
make something for the benefit of others, we are willing to explain to others how it works, so that
38+
they can build on the work to make it even better. We are willing to provide constructive criticism
39+
on the work of others and accept criticism of our own work, as the experiences and skill sets of
40+
other members contribute to the whole of our efforts.
41+
42+
#### Inquisitive
43+
44+
Nobody knows everything! Asking questions early avoids many problems later, so questions are
45+
encouraged, though they may be directed to the appropriate forum. Those who are asked should be
46+
responsive and helpful, within the context of our shared goal of improving neuroimaging practice.
47+
48+
#### Considerate
49+
50+
Members of the community are considerate of their peers. We are thoughtful when addressing the
51+
efforts of others, keeping in mind that often-times the labor was completed simply for the good of
52+
the community. We are attentive in our communications, whether in person or online, and we are
53+
tactful when approaching differing views.
54+
55+
#### Careful in the words we choose
56+
57+
We value courtesy, kindness and inclusiveness in all our interactions. Therefore, we take
58+
responsibility for our own speech. In particular, we avoid:
59+
60+
* Personal insults.
61+
* Violent threats or language directed against another person.
62+
* Sexist, racist, or otherwise discriminatory jokes and language.
63+
* Any form of sexual or violent material.
64+
* Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such
65+
as IRC channel history.
66+
* Excessive or unnecessary profanity.
67+
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
68+
* Advocating for, or encouraging, any of the above behaviour.
69+
70+
#### Concise
71+
72+
Keep in mind that what you write once will be read by many others. Writing a short email means
73+
people can understand the conversation as efficiently as possible. Even short emails should always
74+
strive to be empathetic, welcoming, friendly and patient. When a long explanation is necessary,
75+
consider adding a summary.
76+
77+
Try to bring new ideas to a conversation, so that each message adds something unique to the
78+
conversation. Keep in mind that, when using email, the rest of the thread still contains the other
79+
messages with arguments that have already been made.
80+
81+
Try to stay on topic, especially in discussions that are already fairly long and complex.
82+
83+
#### Respectful
84+
85+
Members of the community are respectful. We are respectful of others, their positions, their
86+
skills, their commitments, and their efforts. We are respectful of the volunteer and professional
87+
efforts that permeate the NIPY community. We are respectful of the processes set forth in the
88+
community, and we work within them. When we disagree, we are courteous and kind in raising our
89+
issues.
90+
91+
## Incident Reporting
92+
93+
We put great value on respectful, friendly and helpful communication.
94+
95+
If you feel that any of our Nibabel communications lack respect, or are unfriendly or unhelpful,
96+
please try the following steps:
97+
98+
* If you feel able, please let the person who has sent the email or comment that you found it
99+
disrespectful / unhelpful / unfriendly, and why;
100+
101+
* If you don't feel able to do that, or that didn't work, please contact Oscar Esteban directly
102+
by email (<[email protected]>), and he will do his best to resolve it.
103+
If you don't feel comfortable contacting Oscar, please email Chris Markiewicz
104+
(<[email protected]>) instead.
105+
106+
## Attribution
107+
108+
The vast majority of the above was taken from the NIPY Code of Conduct.

0 commit comments

Comments
 (0)