Skip to content

Rename enforcement team to CARE team #9750

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

Merged
merged 1 commit into from
May 9, 2018

Conversation

linaori
Copy link
Contributor

@linaori linaori commented May 9, 2018

There were some negative comments about calling it the "enforcement team". This is what it is, but it made some people feel like it was too harsh, too close to policing and easy to give knee-jerk reactions to. Reading the "less obvious checklist" posted by @lsmith77 in https://github.com/symfony/diversity/issues/6#issuecomment-387390245, I noticed DjangoCon had a positive name for this team/group.

Your CoC is useless if you can not respond to issues. Set up a CoC team. In DjangoCon Europe, they’re sometimes called CoC Active Response Ensurers or CARE. An ideal size for this is four people. These people are the primary responsible persons for dealing with any reports, and should be able to have their hands free at any time. They can involve other team members if needed, but having a small CARE team makes it easier to respond consistently, professionally and timely, without distracting the rest of the team.

Source: https://github.com/mxsasha/lessobviouschecklist/blob/master/README.md#code-of-conduct

I would like to propose an adoption of this name as it sounds more positive and caring (:smile:)

Note that I made this towards the master, if I need to change this to 2.7 or 2.8 let me know.

In the interest of fostering an open and welcoming environment, the enforcement team
pledge to ensure that the spirit of the :doc:`Code of Conduct </contributing/code_of_conduct/index>`
In the interest of fostering an open and welcoming environment, the CoC Active Response Ensurers, or CARE,
pledged to ensure that the spirit of the :doc:`Code of Conduct </contributing/code_of_conduct/index>`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

imho this should stay as pledge as its ongoing .. ie. not just in the past

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence reads a bit odd (I'm not a native English speaker after all), I was in the assumption it was past tense or:

the CoC Active Response Ensurers, or CARE, pledge is to ensure that the spirit of

Should I add the "is"?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with this change it sounds more like this pledge is externally defined .. like the pledge of an organization, rather than the individual members. the intention is that this is the "active" pledge of all members of this team.

but if others also think this reads too bumpy, then I can also accept a change to pledge is

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I see what you mean, I just read the sentence wrong. I think you're right so nevermind my suggestion

@@ -56,20 +56,20 @@ when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by enforcement team members.
further defined and clarified by CARE team members.

Enforcement
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the word “enforce” is now limited to this section .. I think it makes sense to keep it here since we also need to show that if necessary we will enforce the CoC .. so +1 from me on this approach.

@lsmith77
Copy link
Contributor

lsmith77 commented May 9, 2018

@iltar yes please make the PR against 2.7

@javiereguiluz javiereguiluz modified the milestones: 2.2, 2.7 May 9, 2018
Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love it. Thanks Iltar!

any of them directly using the contact details below or you can also contact all of
them at once by emailing **coc@symfony.com**.

About the Enforcement Team
About the CARE Team
--------------------------
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The RST syntax is a bit picky ... so we need to make this ------ line as long as the new heading. Thanks!

Copy link
Member

@Nyholm Nyholm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im happy with naming it CARE.
Im also happy with this PR after the proposed changes has been fixed.

@linaori linaori changed the base branch from master to 2.7 May 9, 2018 07:03
@linaori
Copy link
Contributor Author

linaori commented May 9, 2018

Changed the base branch to 2.7 and addressed feedback

@javiereguiluz
Copy link
Member

Thanks @iltar.

@javiereguiluz javiereguiluz merged commit dad5cfb into symfony:2.7 May 9, 2018
javiereguiluz added a commit that referenced this pull request May 9, 2018
This PR was merged into the 2.7 branch.

Discussion
----------

Rename enforcement team to CARE team

There were some negative comments about calling it the "enforcement team". This is what it is, but it made some people feel like it was too harsh, too close to policing and easy to give knee-jerk reactions to. Reading the "less obvious checklist" posted by @lsmith77 in symfony/diversity#6 (comment), I noticed DjangoCon had a positive name for this team/group.

> _Your CoC is useless if you can not respond to issues. Set up a CoC team. In DjangoCon Europe, they’re sometimes called CoC Active Response Ensurers or CARE. An ideal size for this is four people. These people are the primary responsible persons for dealing with any reports, and should be able to have their hands free at any time. They can involve other team members if needed, but having a small CARE team makes it easier to respond consistently, professionally and timely, without distracting the rest of the team._
>
> Source: https://github.com/mxsasha/lessobviouschecklist/blob/master/README.md#code-of-conduct

I would like to propose an adoption of this name as it sounds more positive and caring (:smile:)

Note that I made this towards the master, if I need to change this to 2.7 or 2.8 let me know.

Commits
-------

dad5cfb Rename enforcement team to CARE team
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants