Skip to content

Introduction of code of conduct for pytest #5709

@asottile

Description

@asottile

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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: help wanteddevelopers would like help from experts on this topictype: docsdocumentation improvement, missing or needing clarificationtype: infrastructureimprovement to development/releases/CI structuretype: proposalproposal for a new feature, often to gather opinions or design the API around the new feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions