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

Change our Code of Conduct #113

Open
varjmes opened this issue Feb 19, 2017 · 6 comments
Open

Change our Code of Conduct #113

varjmes opened this issue Feb 19, 2017 · 6 comments

Comments

@varjmes
Copy link

varjmes commented Feb 19, 2017

I think our code of conduct is lacking in several cases. Most notably, our 'enforcement' instructions are very basic. I've started implementing a new code of conduct across my projects that I had a small hand in writing, but it is mainly made by the wealljs community and @zkat. It has really good enforcement instructions, outlines what isn't acceptable in a better way than we do and has good examples of unacceptable behaviour. I think it is is much better than what we currently have.

https://github.com/zkat/pacote/blob/latest/CODE_OF_CONDUCT.md

I propose we change our code of conduct to this. Or use it as a base and modify to our needs if you feel it is lacking.

Also, I noticed that we don't really surface our code of conduct in any of our repositories (it is mentioned once at the bottom of our hoodiehq/hoodie readme, with regards to monetary sponsors). I think we should put the code of conduct in every repo, and link to it at the top of our project READMEs. Although this may be some work, it is a perfect starter PR for a whole host of new contributors (in every repo!)

@gr2m
Copy link
Member

gr2m commented Feb 19, 2017

Thanks for bringing that up. I’ve read both Code of Conducts side-by-side and I agree that the one you linked is much better from my perspective. A particularly like the examples. Being a maintainer that have not yet been in a situation to enforce a CoC, it is great to know that I can refer to them when something comes up. We can extend the examples as needed. I think these examples would be very helpful to on-board new maintainers to Hoodie.

I’m curious to hear what others think.

I think we should put the code of conduct in every repo, and link to it at the top of our project READMEs

Yes, absolutely agree.

@janl
Copy link
Member

janl commented Feb 19, 2017

This is great <3 major +1

@mbad0la
Copy link

mbad0la commented Feb 19, 2017

It's a good step forward!

I think these examples would be very helpful to on-board new maintainers to Hoodie

The changes will also encourage new and old contributors alike to step forward and be more involved and active, as people would be more comfortable in such a well-defined and considerate environment. Not that Hoodie hasn't been a good experience for me uptil now (infact, the best open source experience for me), but this would make things a bit more established.

@jennwrites
Copy link

+1

Thanks @Charlotteis. I have massive respect for the wealljs folks and @zkat too, so can we make sure to credit your hard work in the new Coc? Because this is new version is super valuable imo.

@varjmes
Copy link
Author

varjmes commented Feb 28, 2017

I'll draw up a plan this weekend

@gr2m
Copy link
Member

gr2m commented Jun 17, 2017

Hey @Charlotteis do you still want to incorporate the changes you suggested? I think we are all +1 :)

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

No branches or pull requests

5 participants