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 an initial contributor CoC #2767
Conversation
There are a few extra spaces scattered throughout the document. Other then that, I have no issues with it. |
👍 on respect. |
+1. Thanks @phinze! |
123a149 now with less spaces! |
Just returning from a day of Jury duty; serendipitous timing. This is a good disclaimer for a large project. I checked out the CoC project pop up on my feed when it was first open sourced (days ago), and I questioned the file naming at that time. For the cask project, underscores and lowercase aren't consistent with f.ex |
👍 On Thursday, February 6, 2014, Joel Kuzmarski notifications@github.com
|
Big thumbs up on this. I agree with @leoj3n, however, and I’m just slightly thorn on the naming issue. Having a consistent name accross all projects is a big plus if anyone wants to programatically check which projects adhere to this. This is akin to having a Having said that, I’m personally more inclined to keeping consistent naming accross the project. Other than that, as stated, I'm all for including this, in whatever form. |
this is so everybody knows this project is LEGIT and that you--yes YOU--are welcome to help us build this weird little thing. <3 to @BanTiK for the idea and the draft
Agreed on consistent naming. How about this? 244d29c renames file to |
Looks good. |
cool - doing it! 🍞 📙 ⚓ 🎱 ⌚ 〰️ 🌊 |
this is so everybody knows this project is LEGIT and that you--yes
YOU--are welcome to help us build this weird little thing.
<3 to @BanTiK for the idea and the draft
calling all collaborators:
@vitorgalvao @passcod @nanoxd @fanquake @leoj3n @rolandwalker @kevinSuttle
HELLO ALL YOU GOOD PEOPLE, 😀
This is just a doc that asserts the sort of stuff we already do.
Take a looksie and raise any issues you might have.
Maybe you want to know more of why to do this, here is a start:
http://www.ethics.org/resource/why-have-code-conduct