viewpoints • If you maintain/contribute to an open source project ◦ DON’T: Assume it’s a lost cause and ignore it ◦ DO: Make small changes at an appropriate pace ◦ DON’T: Declare unilaterally that things are changing ◦ DO: Ask for alternative suggestions from people who may object to changes ◦ DON’T: Completely disregard opinions of existing contributors ◦ DO: Stand firm that existing contributors should be welcoming • Use as a framework to help your company be more attractive to a diversity of candidates @charlottecodes
contributors • Generally sees communication from people who look it up A slippery project: • May have a few long-term contributors • Sees minimal or no communication from people who look it up @charlottecodes
Cons: • Opaque to new users (difficult to understand for people not used to older tech) • No archive of old messages • In many instances, no authentication of users
(similar to other modern team chat apps) • Available multi-platform (web/desktop/mobile) • Can be self-hosted if desired Cons: • Requires signup/registration
you’re asking. When you say X, are you referring to Y or something else?” • “If I understand your question, you might find the answer at [best-guess-documentation]. If your answer isn’t there, come let us know and we’ll try to help you figure it out!” • “I’m not sure why that’s happening. Could you show us what you did that resulted in that?”
this will mesh well with [other-feature]. Did you talk through this with anyone on [chat-or-mailing-list]?” • “This isn’t something that we want to support. If you’d like to turn it into a plugin instead, you’re welcome to do that and handle the support yourself.” • “There are a lot of things in this PR that conflict with our style guide [link]. If you need help identifying them, feel free to ask in [chat-or-mailing-list].”
points apply just as much, if not more, when enforcing CoC • Be kind, and don’t accept attacks from any source during resolution ◦ Accusations, if reasonable, are not attacks • Be prepared to remove/ban people from your project if necessary • Consider CoC enforcement workshops if this all sounds overwhelming! @charlottecodes
project (Django): https://www.djangoproject.com/conduct/ • Good example for an event (PyCon): https://us.pycon.org/2019/about/code-of-conduct/ • Good example for an organization (Vox): http://code-of-conduct.voxmedia.com/ • Tips for writing/adapting your own: https://projectinclude.org/writing_cocs# • Example of an organization providing workshops: https://otter.technology