Skip to content
This repository has been archived by the owner on Oct 7, 2022. It is now read-only.

Adopt code of conduct for MagicBox projects #7

Open
jwflory opened this issue Jan 8, 2018 · 0 comments
Open

Adopt code of conduct for MagicBox projects #7

jwflory opened this issue Jan 8, 2018 · 0 comments
Labels
community Supporting and building the project community needs info Extra information needed priority:low We're not thinking about it yet

Comments

@jwflory
Copy link
Member

jwflory commented Jan 8, 2018

Summary

Adopt code of conduct (Contributor Covenant?) to set clear expectations for acceptable and unacceptable behavior in MagicBox projects

Background

Having a code of conduct for an open source project is important. A company or organization has a human resources department and expectations for how employees are to behave, but an open source project does not. Setting clear expectations for what behavior is appropriate or not is important, and also assures confidence in contributors that their experience will be positive.

See GitHub's open source guide for a more in-depth explanation of the value of a code of conduct.

Details

Writing a code of conduct is hard to do the right way. I am a fan of the Contributor Covenant, which does the work of writing it and helping us set clear expectations. I think it will be easy to implement and use this CoC for MagicBox projects.

Extra consideration is needed about where code of conduct violation reports should go (to what email address), and also how violations will be handled. It's impossible to map out every scenario, but if someone does report a violation of the CoC, it should be handled respectfully and promptly. Setting a CoC without having a plan for how to actually enforce it is not a good idea.

Action

Agree or write a code of conduct to set clear expectations and guidelines for contributor behavior in MagicBox projects, have a general idea of how to handle violation reports should they ever happen

@jwflory jwflory added needs info Extra information needed priority:low We're not thinking about it yet community Supporting and building the project community labels Jan 8, 2018
@jwflory jwflory added this to the Internship: @jflory7 milestone Jan 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
community Supporting and building the project community needs info Extra information needed priority:low We're not thinking about it yet
Projects
None yet
Development

No branches or pull requests

1 participant