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

add Code of Conduct #2362

Merged
merged 1 commit into from
Mar 3, 2017
Merged

Conversation

alison985
Copy link
Contributor

Needs to be updated with an email address for a maintainer.

Found this issue #2323 as part of looking for something to do today for #100DaysofCommits but saw Read The Docs has no COC yet. Adding COC first.

Needs to be updated with an email address for a maintainer.
@agjohnson
Copy link
Contributor

Any reason this wasn't just added to our documentation? I'm not finding if this is a file that GitHub supports in some sort of native fashion

@ericholscher
Copy link
Member

+1 on a more explicit code of conduct. It should be included in the docs, and I'd be more inclined to probably use Django's or the Python community one. Though we should figure out which to use.

@agjohnson agjohnson added the PR: work in progress Pull request is not ready for full review label Aug 18, 2016
@alison985
Copy link
Contributor Author

It actually didn't occur to me to put it straight in the documentation as that's not the convention I'm familiar with. I'm used to seeing it as a specific file (see https://github.com/search?q=code_of_conduct.md&ref=searchresults&type=Code&utf8=%E2%9C%93 with 30k+ results).

What is the best way to get a decision on which code of conduct will apply to this repo?

@agjohnson
Copy link
Contributor

I think this is much better suited for our documentation, that is where all of our other contributing docs are. Also, GitHub doesn't seem to handle these files natively, such as it does with the .github/CONTRIBUTING.rst file.

Our current contributing docs should link to the CoC, they live at:
http://docs.readthedocs.io/en/latest/contribute.html

On the copy of the agreement, I prefer the tone of Django's code of conduct to the one supplied here, and don't think Python's defines expectations explicitly enough. It's also important the CoC sets the expectation on all users, not just maintainers/contributors.

My vote is for Django's CoC here.

@skirpichev
Copy link
Contributor

People, do you have some pragmatical reasons to add this nonsense? Do you care if CoC will stop someone from contributing to your project?

What about simple NoCoC instead?

@agjohnson
Copy link
Contributor

@skirpichev the internet has shown time and time again that it isn't always capable of acting like an adult, and so yes, we whole-heartedly agree it's necessary that we explicitly state what is unacceptable behavior. This has never been a problem though, and we hope it is never a problem.

If anyone lost interest in contributing because they would rather use hateful language/actions, it's probably for the best anyways.

Copy link
Contributor

@agjohnson agjohnson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CoC should be moved to our documentation, and linked to from CONTRIBUTING.md possibly too.

@skirpichev
Copy link
Contributor

This has never been a problem though

So, you don't have practical reasons (from the history of the project) to introduce this, right?

because they would rather use hateful language/actions

No, because they learn that such documents - provoke instead "hateful actions" by hiding conflicts, not stop them. Anyway, thank you for explanation of your decision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants