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

introduce Code of Conduct #1197

Merged
merged 3 commits into from Jan 9, 2017
Merged

introduce Code of Conduct #1197

merged 3 commits into from Jan 9, 2017

Conversation

shiftkey
Copy link
Member

@shiftkey shiftkey commented Mar 17, 2016

If you're not familiar with it, the Contributor Covenant is a good starting point for communities to identify the values they uphold, as well as what happens when conflicts arise.

Opening this up to start a discussion on what should be in it.

  • [ ] discussion about things to add/change/remove
  • [ ] introduce preamble which is Octokit-specific
  • replace [INSERT EMAIL ADDRESS] with actual email address
  • mention this in README.md

* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
Copy link
Contributor

Choose a reason for hiding this comment

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

Serious question: Some of use come from a more relaxed definition of professional setting in general, or at least when it comes to projects done on private time.
Is it worth it/is there a way at all to reword this bit so as not to cause confusion due to the dry (American based) meaning?

Copy link
Member Author

Choose a reason for hiding this comment

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

Given this is a "virtual" group of contributors and spanning just about all the continents, I'm open to elaborating on what this might mean to our situation. This also feels like a bit of a catch-all phrase, so perhaps we can be more specific here.

Will ponder on it, but open to suggestions...

Copy link
Contributor

Choose a reason for hiding this comment

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

I'd like to leave it as-is so we stay true to the original CoC. We take a pretty relaxed approach to our "professional setting" so telling jokes and being silly is fine as long as the jokes aren't demeaning or exclusive of others along the lines described. So probably fine to make the joke about VB the programming language, but not jokes that demean women.

Also, we understand that people make mistakes and have different ideas about what is considered appropriate. We're not going to hell-ban you for the first infraction unless it's way over the line.

Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

Consider this document the start of the conversation, not the end. For the most part, I don't see anything in here so far that goes against the spirit of this. Everyone that's participated has been pretty great. We've had a few bad eggs, but most were still somewhat respectful.

@haacked
Copy link
Contributor

haacked commented May 10, 2016

✨ I'm excited to see this added. We want to signal to people that they are welcome to contribute and that we care about having an inclusive welcoming environment for all contributors.

@M-Zuber
Copy link
Contributor

M-Zuber commented May 11, 2016

:shipit:

@haacked
Copy link
Contributor

haacked commented May 12, 2016

@shiftkey should the email address be support@github.com?

@shiftkey
Copy link
Member Author

@haacked I'd love it to be more specific than that, so that it goes directly to the right people

@haacked
Copy link
Contributor

haacked commented May 12, 2016

@haacked I'd love it to be more specific than that, so that it goes directly to the right people

Please don't make it go just to me. 😛 What did you have in mind?

@shiftkey
Copy link
Member Author

@haacked something like conduct+octokit.net@github.com but I need to bug some people internally to ensure we're all on the same page before confirming it...

@M-Zuber
Copy link
Contributor

M-Zuber commented Aug 24, 2016

@shiftkey bump

@shiftkey shiftkey self-assigned this Sep 16, 2016
@shiftkey
Copy link
Member Author

Yeah, this fell off our radar due to Other Priorities™.

I'm taking next week off (computer-free) so I'll pick this up when I'm back.

@SeanKilleen
Copy link
Contributor

Bumping this; would be nice to actually get it in.

For the sake of merging this, could it make sense to use support@github.com for now and add a follow-up issue to add a more specific e-mail address when one is available? Seems like a quick win to get this in; plus, you know that someone will be manning the e-mail there.

If you want to give them the ability to filter, maybe using an e-mail trick like support+octokitnet+conduct@github.com could do what you're looking for? Would still go to support but they'd be able to route based on the to address.

@ryangribble
Copy link
Contributor

I agree it'd be nice to merge this in. Obviously GitHub staffers will need to make the call about what email address to use (and whether we can use support@github.com for now)... ping @shiftkey @haacked

@shiftkey shiftkey changed the title [WIP] introduce Code of Conduct introduce Code of Conduct Jan 9, 2017
@shiftkey
Copy link
Member Author

shiftkey commented Jan 9, 2017

Updated the guidelines to use a real email address. Aside from some logistics work on my end this is ready to merge. Over to you @haacked.

@haacked haacked merged commit 38f0826 into master Jan 9, 2017
@haacked haacked deleted the shiftkey-code-of-conduct branch January 9, 2017 21:37
@haacked
Copy link
Contributor

haacked commented Jan 9, 2017

🎉

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.

None yet

5 participants