RFC: Updates to Community Code of Conduct #1467
Conversation
|
Thanks for the pull request! Here is what will happen next:
Thank you for contributing! |
CODE_OF_CONDUCT.md
Outdated
|
|
||
| In the interest of fostering an open and welcoming environment, we as | ||
| In the interest of fostering an open, welcoming, and encouraging environment, we as |
There was a problem hiding this comment.
welcoming, encouraging, and supportive environment?
There was a problem hiding this comment.
i think encouraging presupposes supportive?
There was a problem hiding this comment.
For me, just "open and welcoming" is the most clear variant.
There was a problem hiding this comment.
Open and welcome does not include encouraging. Encouraging sets a standard for mental/emotional support in terms of language choices when interacting with folks who bring new or less than perfect contributions to the table.
There was a problem hiding this comment.
I'm fond of encouraging as well - and for the record, Habitat has been one of the most encouraging, welcoming and open communities I've ever participated in.
CODE_OF_CONDUCT.md
Outdated
| * Your work will be used by other people, and you, in turn, will depend on the work of others. | ||
| * Decisions that you make will often affect others in the community. | ||
| * Disagreements happen, but should not be an excuse for poor behavior and bad manners. When disagreements do happen, let’s work together to solve them effectively and in a way that ensures that everyone understands what the disagreement was. | ||
| * People may not understand jokes, sarcasm, and oblique references in the same way that you do. So remember that and be kind to the other members of the community. |
There was a problem hiding this comment.
Out of principle i get this, but it's hard to gauge what's considered ok here.
There was a problem hiding this comment.
Sure, I don't think this section is about hard values though. I think this is more of a: things to keep in mind while you're interacting with other community members. Perhaps we should make that more clear?
There was a problem hiding this comment.
make amends can be tricky and can often make things worse - we should be careful here, this is where I'd want Code of Conduct crew or someone trained to deal with these things sitting
There was a problem hiding this comment.
I think make amends is right. Maybe borrow from Kronda's tweet here https://twitter.com/kronda/status/546727506850496512
There was a problem hiding this comment.
I'll agree with the sentiment of the tweet, need to rephrase it.
How about a bit of paraphrasing:
- Our community spans languages, cultures, perspectives, and many other facets, and sometimes inside jokes, sarcastic comments, or oblique references may not be perceived as planned by the author. Keep this in mind, and be kind to others, treat them with the same respect you would expect to receive.
CODE_OF_CONDUCT.md
Outdated
| * Consult with another maintainer to make a judgement call about what reasonable corrective actions are warranted. | ||
| * Apply the corrective action. | ||
| * Document the incident. | ||
|
|
There was a problem hiding this comment.
Should we put in a standard email or google voice number to call and call it out here? If we standardize on it, it could in the case of an incident to say "email this" "call that number" and you'll find someone to help.
There was a problem hiding this comment.
Ideally what we are moving towards is something similar to the way Chef handles this. We will likely have contributors and maintainers that exist as community advocates who can field these things. Once we've got folks who are willing to do that, we'll create a chart in here that explains who those people are. For now though maybe it'd be good for us to link to the maintainers doc?
There was a problem hiding this comment.
If it's not explicit how to get help, then as a whole not helpful. Doesn't show follow-through. There should also be a companion to this policy with training for folks on how to handle different scenarios.
|
Added some comments but otherwise +1 |
CODE_OF_CONDUCT.md
Outdated
| * Using welcoming and inclusive language | ||
| * Exercising patience and friendliness | ||
| * Being respectful of differing viewpoints and experiences | ||
| * Gracefully accepting constructive criticism | ||
| * Focusing on what is best for the community | ||
| * Showing empathy towards other community members | ||
|
|
There was a problem hiding this comment.
Maybe try active voice here? For example, "Use welcoming and inclusive language" and "Exercise patience and friendliness".
There was a problem hiding this comment.
yeah I wondered about that, I think that would be a good change thank you!
CODE_OF_CONDUCT.md
Outdated
| Examples of behavior that contributes to creating a positive environment | ||
| include: | ||
| Be careful in the words that you choose. Be kind to others. Practice empathy. Don't | ||
| insult or put down others. Remember that sexist, racist, and other exclusionary jokes |
CODE_OF_CONDUCT.md
Outdated
| * Decisions that you make will often affect others in the community. | ||
| * Disagreements happen, but should not be an excuse for poor behavior and bad manners. When disagreements do happen, let’s work together to solve them effectively and in a way that ensures that everyone understands what the disagreement was. | ||
| * People may not understand jokes, sarcasm, and oblique references in the same way that you do. So remember that and be kind to the other members of the community. | ||
| * Sexist, racist, and other prejudicial or exclusionary comments are not welcome in the community. |
CODE_OF_CONDUCT.md
Outdated
|
|
||
| #### Documenting Incidents | ||
|
|
||
| All incident reports will be kept in a private repository that is shared with the advocates, maintainers and Community Manager. |
There was a problem hiding this comment.
This seems scary. This needs to be an explicit list and minimal if it has identifying information in it. It needs to be stuck in a moment of time where someone new doesn't get access to it.
There was a problem hiding this comment.
Can you elaborate on this a bit? It seems like having historical context of incidents is useful in determining further actions.
There was a problem hiding this comment.
Sure. If I report an incident, I want to know exactly who is going to know about and what they are going to do with that information. If this is something that is going to have identifying information over a long haul, this means that I might be more hesitant to report something if I don't have some kind of knowledge about who might have access to that information. For example, how do I know that in 6 months someone who was involved with the incident doesn't get access to the details?
There was a problem hiding this comment.
Totally that makes sense. I was also talking with @Hoverbear about this. I think this section should change to include information on how to report an incident (and who SPECIFICALLY to report it to) within the community and information for how to report in the case that the person in question (the individual who is breaking the community covenant) are one in the same. E.g. John Doe is a community advocate I should report harassment to, but John Doe is the person doing the harassing in this case. And that second point of contact should be outside of the team that typically handles these things.
There was a problem hiding this comment.
So essentially what I'm saying is @iennae is right. The list of people that have access to the incident lists needs to be more explicit and significantly less inclusive.
|
I think I agree here - fostering learning environments is important (and also helps surface less obvious pain points in what we're building).
|
CODE_OF_CONDUCT.md
Outdated
|
|
||
| As you are working with other members of the community, please keep in mind the following guidelines, which apply equally to founders, mentors, those who submit new features and pull requests, and to anyone who is seeking help and guidance. |
There was a problem hiding this comment.
Minor style nitpick: other lines terminate around the 80 char mark, these do not.
CODE_OF_CONDUCT.md
Outdated
| * Trolling, insulting/derogatory comments, and personal or political attacks | ||
| * Public or private harassment | ||
| advances. | ||
| * Violent threats or language directed against another person. |
There was a problem hiding this comment.
What about non-violent threats?
- Threats or violent language directed against another person
CODE_OF_CONDUCT.md
Outdated
| advances. | ||
| * Violent threats or language directed against another person. | ||
| * Posting sexually explicit or violent material. | ||
| * Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language. |
There was a problem hiding this comment.
"...transphobic, ableist, or otherwise..." don't leave off the oxford comma.
|
Iteration 2 of this is inbound early next week. We will be correcting some of the verbage as discussed above as well as defining a community hierarchy for reporting and handling incidents. I'll post here when the new commit is in :) |
|
OK. SO. Theres a new Code of Conduct iteration that I've just pushed to this branch. I would super appreciate if those of you who previously had comments would check the new CoC to determine if your primary concerns have been resolved. Important changes to note: We now have an explicit list of Community Organizers! Huzzah! We also now have an explicit guide for how to handle an incident with help from those community organizers! Huzzah! I've tightened verbage based on the previous concerns listed. Assuming there are no greater concerns this is the content that I think we should use. |
CODE_OF_CONDUCT.md
Outdated
| * Your work will be used by other people, and you, in turn, will depend on the work of others. | ||
| * Decisions that you make will often affect others in the community. | ||
| * Disagreements happen, but should not be an excuse for poor behavior and bad manners. When disagreements do happen, let’s work together to solve them effectively and in a way that ensures that everyone understands what the disagreement was. | ||
| <<<<<<< HEAD |
There was a problem hiding this comment.
Did you mean to leave this in? :)
CODE_OF_CONDUCT.md
Outdated
| 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 project maintainers. | ||
| further defined and clarified by project maintainers and community organizers. | ||
|
|
||
| ## Enforcement |
There was a problem hiding this comment.
The mechanism to report feels like it should be nearer to the top.
CODE_OF_CONDUCT.md
Outdated
| * The behavior that was in violation | ||
| * The approximate time of the behavior | ||
| * The circumstances surrounding the incident | ||
| * Other people involved in the incident |
There was a problem hiding this comment.
Might want to be clear about whether the victim's information will be stored in repository.
There was a problem hiding this comment.
My initial feeling is to say that we should track an initial point of contact for the victim. Do you have any opinions on that?
There was a problem hiding this comment.
I think the victims information shouldn't be included in the repo and we should explicitly say that. Tracking the information outside of the event of that detail is important, but leaving a paper trail about the victim decreases the safety around reporting events to some degree.
There was a problem hiding this comment.
Perhaps it does. I've been feeling mixed about it. If you and others feel strongly this is the right way to go then I'm in on it.
CODE_OF_CONDUCT.md
Outdated
|
|
||
| * Consult with another Community Organizer to make a judgement call about what reasonable corrective actions are warranted. | ||
| * Apply the corrective action. | ||
| * Document the incident. |
There was a problem hiding this comment.
Document the incident as described below.
CODE_OF_CONDUCT.md
Outdated
| If you have any lack of clarity about behaviors we include in the definition of "harassment", please read the [Citizen Code of Conduct](http://citizencodeofconduct.org/). In particular, we don’t tolerate behavior that excludes people in socially marginalized groups. | ||
|
|
||
| ### Roles | ||
| The following are the various roles of our Community Organizers and the people assigned to each role: |
There was a problem hiding this comment.
maybe bold Community Organizers here at the top or have a separate paragraph to define them as the collection of all roles. Later when you use Community Organizers it's a little confusing as I was looking for the specific roles here.
CODE_OF_CONDUCT.md
Outdated
|
|
||
| The Advocate should take the following steps if the behavior is not brought inline with our guidelines or the incident is not resolved. | ||
|
|
||
| * Consult with another Community Organizer to make a judgement call about what reasonable corrective actions are warranted. |
There was a problem hiding this comment.
This might need to be expanded out a little. What if 1 organizer thinks that the situation doesn't warrant action? "Consult with at least one other Community Organizer to identify the set of correction actions to be taken.
There was a problem hiding this comment.
Yes excellent. The process should be an escalation of the snowball variety I think. E.g. if two cant agree, get a third, if 3 cant agree get a 4th, if 4 cant agree get the Decider.
CODE_OF_CONDUCT.md
Outdated
| ### Roles | ||
| The following are the various roles of our Community Organizers and the people assigned to each role: | ||
| * The <b>Decider</b> has final say on community guidelines and final authority on correct actions and appeals. The top-level decider is [Adam Jacob]([email protected]), [@adamhjk](https://twitter.com/adamhjk) | ||
| * The <b>Community Manager</b> guides and meets regularly with community advocates, helps enforce corrective actions, hears appeals, is responsible for maintaining a list of incidents, and ensures pertinent information is shared with necessary parties. The Community Manager is [Ian Henry]([email protected]), [@eeyun___](https://twitter.com/eeyun___). |
There was a problem hiding this comment.
Maybe have a separate section on sharing of information. what, and who. I know it's mentioned later but calling it out explicitly is good.
I imagine it's something like:
- Repo of incidents - community organizers
- acknowledgement of report, and any followup - person reporting
- set of corrective actions and consequences of failing to follow through - person being reported
There also feels like an explicit need to say that that folks who are community organizers that are removed from the role will upon removal eliminate any local copies of the repo that they have in addition to the having role revocated with github.
There was a problem hiding this comment.
Oh yeah thats totally worth noting. Hadn't thought about local copies.
Can you clarify what you mean about sharing of information?
There was a problem hiding this comment.
In the Community Manager role it says "ensures pertinent information is shared with necessary parties" .. I'm suggesting having a specific section that documents the "Sharing of Information" and what it means. I think many times one of the challenges of folks to come forward with incidents is fear and how the information about what happened and who they are will get used for retaliation. So when you have something that says "pertinent information is shared with necessary parties" questions come up.. what is pertinent information, who has access to it, etc.
There was a problem hiding this comment.
Perfect that's excellent!
Signed-off-by: Ian Henry <[email protected]> punctuation and typos Signed-off-by: Ian Henry <[email protected]> Code of Conduct New Iteration Signed-off-by: eeyun <[email protected]> Updates to Code of Conduct to be more explicit on acceptability Signed-off-by: Ian Henry <[email protected]> corrected ben's email address Signed-off-by: eeyun <[email protected]>
eeyun
force-pushed
the
eeyun/code_of_conduct
branch
from
cc32463 to
019e975
Compare
|
As no further responses have popped up to this PR. I think it's ready to be merged! As we are still a relatively young community there should be a bit of flexibility when it comes to altering the CoC moving forward but for now this is a solid starting point! |
christophermaier
added
Documentation
This is the first pass on a PR that more explicitly defines the boundaries of our community interactions.
What we had was not bad by any stretch of the imagination. But I find myself wanting something more explicit in both the process and expectation around how our community handles itself.
These changes should not realistically be anything new to the community, however a PR of this nature should more clearly delineate what is accepted/expected from community members and that's what I'm hoping to do here.
PLEASE LEAVE COMMENTS AND ADD REVIEWS.
I can't personally think of a PR that is more important to Habitat than a PR defining what we want from our community.