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
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