Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduction of code of conduct for pytest #5709

Closed
asottile opened this issue Aug 8, 2019 · 4 comments
Closed

Introduction of code of conduct for pytest #5709

asottile opened this issue Aug 8, 2019 · 4 comments
Labels
status: help wanted developers would like help from experts on this topic type: docs documentation improvement, missing or needing clarification type: infrastructure improvement to development/releases/CI structure type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature

Comments

@asottile
Copy link
Member

asottile commented Aug 8, 2019

I figure we're a large enough organization that runs a decent amount of public relations through github issues / PRs that it would make sense that we set up some clear guidelines on contributions and conduct. I've never worked with a CoC before but I think it would be good to formalize a set of guidelines that ensure that we as individual contributors are producing high quality external and internal interactions.

As I don't know the first thing about the right thing to do for a CoC I'm opening this as more of a RFC / open ended discussion where we can choose the right approach here. My main goals are that we end at a place where we can all have positive interactions with individuals and foster a positive community (much like we're hopefully already doing!).

A few examples we might be able to follow here:

@asottile asottile added status: help wanted developers would like help from experts on this topic type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature type: docs documentation improvement, missing or needing clarification type: infrastructure improvement to development/releases/CI structure labels Aug 8, 2019
@RonnyPfannschmidt
Copy link
Member

i'd like to note that @The-Compiler also already did set up [email protected] as an alias

and Brianna, @nicoddemus, @The-Compiler and me are receiving messages for it

also based on current information i'm happy to adopt the contributor covenant in a recent version even if i disagree with various behaviors of its creators

it will be critical to build a awareness of the spirit we want to bring across by adding the letters of a CoC, and then to make sure we keep the spirit in mind when interpreting the letters when enforcement is necessary

The-Compiler added a commit that referenced this issue Aug 8, 2019
See #5709 and the mails linked from there
@The-Compiler
Copy link
Member

Oh, I totally forgot about having that set up already 😆 I opened a PR to get the ball rolling: #5711

And now I'm back to my exams (I'll take a look at emails though!) 👨‍🎓

@asottile
Copy link
Member Author

asottile commented Aug 8, 2019

via #5711

@asottile asottile closed this as completed Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: help wanted developers would like help from experts on this topic type: docs documentation improvement, missing or needing clarification type: infrastructure improvement to development/releases/CI structure type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature
Projects
None yet
Development

No branches or pull requests

3 participants