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

Consider breaking out the Enforcement Steps into a Separate Document #910

Open
emmairwin opened this issue Feb 12, 2021 · 9 comments
Open

Comments

@emmairwin
Copy link
Contributor

emmairwin commented Feb 12, 2021

Thanks for this great work!

I wonder if you would consider breaking out the Enforcement Guidelines into a separate document. For a few reasons:

  1. Being right in the document lends tone feels to be about consequence, vrs a tool for building inclusive communities.
  2. The consequences feel inflexible, or not open variation because they are right in this as governance. For example I have issued warnings, but those people still interacted with others involved ( for example volunteers working together in a support forum, would find it hard not to interact); in this case how would I explain that I did not follow the CoC rules?
  3. Having a document that describes enforcement, can become a guide for other things (like how to take a report, and what to expect afterwards). Example.

I can probably just do this on a community-basis, but wanted to suggest as an overall change as well, and would be happy to contribute to what that might look like.

Thanks!

@CoralineAda
Copy link
Member

I like the idea a lot, but I'm not sure it could be effectively implemented on our side. What if we made this as a suggestion on the CC site itself under "Using Contributor Covenant"?

@emmairwin
Copy link
Contributor Author

I think that as a suggestion is a good idea, that way its both permission to do that, and a nudge to think about what specifics of the enforcement may or may not make sense in context of their community (like not interacting with others, and warning example I gave).

Thanks for responding!

@CoralineAda
Copy link
Member

@emmairwin Would you like to take a pass at updating the language on the home page?

emmairwin added a commit to emmairwin/contributor_covenant that referenced this issue Feb 20, 2021
As per EthicalSource#910 , took a first pass at what recommendations might be for projects and communities where the default guidelines don't quite fit the context/tone of the community.
emmairwin added a commit to emmairwin/contributor_covenant that referenced this issue Feb 20, 2021
As per EthicalSource#910 proposed new language for those communities where default language of Enforcement Guidelines does not match community context/tone.
@CoralineAda
Copy link
Member

@emmairwin When you have a chance, please take a look at the home page. I rewrote it this weekend and I think it addresses some long-standing confusion around adoption and enforcement. If you have more suggestions, please feel free to open another issue. And thank you so much!

@emmairwin
Copy link
Contributor Author

I like how you have organized that section now, and the prompt for people to understand the importance of that discussion about enforcement, and the tone they want to set. Thank you!

The only other thing that may be good in future, it to describe how the expected behaviors make this document also a great tool for promoting healthy communities, leading by example etc. If you agree of course.

@CoralineAda
Copy link
Member

I really like your suggestion. Is this something you'd be interested in collaborating on?

@CoralineAda CoralineAda reopened this Feb 22, 2021
@emmairwin
Copy link
Contributor Author

for sure! I'll propose something a bit later this week.

@AevaOnline
Copy link

Chiming in because this is an important point - including the Enforcement Steps as part of the main CC 2.0 text has made it difficult for me to support adoption in orgs that I work with, and we tend to stay at 1.4 because of this.

I've observed that less-experienced leaders will tend to fall back to the text of the document, and in some cases feel as though they must abide by the text as-given. Making it explicitly demonstrative, rather than proscriptive, would definitely help. Also, I really like some of the recent changes, such as encouraging inclusive behaviours and prioritizing the needs of any injured party through supporting documentation!

jcfr added a commit to lassoan/Slicer that referenced this issue Jul 20, 2022
This commit removes the "Enforcement Guidelines" and intend to provide
more latitude in the handling of specific complaints by not creating the
expectations that we enforce behavior outside of the project.

Adaptation of the "Enforcement Guidelines" is aligned with the
"Before You Adopt Contributor Covenant" instructions available
since v2.1 (see [1]) and introduced following discussion in [2]:

> Before you decide to adopt Contributor Covenant, take the time to
> discuss enforcement with other trusted members of your community.
> Thoroughly read the Enforcement Guidelines section of the document.
> If the suggested actions and consequences don’t suit the context of
> your community, consider moving this section to another document (such
> as an FAQ or ‘How to Report’ page) and adapting it to your needs.

[1] EthicalSource/contributor_covenant@f46573395
    New recommendations - Enforcement Guidelines

[2] EthicalSource/contributor_covenant#910
    Consider breaking out the Enforcement Steps into a Separate Document

Co-authored-by: Andras Lasso <lasso@queensu.ca>
Co-authored-by: Jean-Christophe Fillion-Robin <jchris.fillion@kitware.com>
Co-authored-by: Lisa Avila <lisa.avila@kitware.com>
Co-authored-by: Sonia Pujol <spujol@bwh.harvard.edu>
Co-authored-by: Steve Pieper <pieper@isomics.com>
Co-authored-by: Yvette Fitzgerald <y.fitzgerald@kitware.com>
jcfr added a commit to Slicer/Slicer that referenced this issue Jul 21, 2022
This commit removes the "Enforcement Guidelines" and intend to provide
more latitude in the handling of specific complaints by not creating the
expectations that we enforce behavior outside of the project.

Adaptation of the "Enforcement Guidelines" is aligned with the
"Before You Adopt Contributor Covenant" instructions available
since v2.1 (see [1]) and introduced following discussion in [2]:

> Before you decide to adopt Contributor Covenant, take the time to
> discuss enforcement with other trusted members of your community.
> Thoroughly read the Enforcement Guidelines section of the document.
> If the suggested actions and consequences don’t suit the context of
> your community, consider moving this section to another document (such
> as an FAQ or ‘How to Report’ page) and adapting it to your needs.

[1] EthicalSource/contributor_covenant@f46573395
    New recommendations - Enforcement Guidelines

[2] EthicalSource/contributor_covenant#910
    Consider breaking out the Enforcement Steps into a Separate Document

Co-authored-by: Andras Lasso <lasso@queensu.ca>
Co-authored-by: Jean-Christophe Fillion-Robin <jchris.fillion@kitware.com>
Co-authored-by: Lisa Avila <lisa.avila@kitware.com>
Co-authored-by: Sonia Pujol <spujol@bwh.harvard.edu>
Co-authored-by: Steve Pieper <pieper@isomics.com>
Co-authored-by: Yvette Fitzgerald <y.fitzgerald@kitware.com>
@janderssonse
Copy link
Contributor

I agree with others - "Enforcement"-details is an implementation detail which should be left out of the general conduct text.

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

6 participants
@CoralineAda @emmairwin @AevaOnline @janderssonse and others