-
Notifications
You must be signed in to change notification settings - Fork 62
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
Added Reporting and What to do #28
Conversation
- section on Reporting - section "what to do if you make a mistake - copied with minor edits from https://immersive-web.github.io/homepage/code-of-conduct.html (thanks @AdaRoseCannon)
suggestion s/violations of code conduct/concerns about the code of conduct |
I don't think this substitution would retain the same meaning. "Violations of code of conduct" is a clear concept describing the case when a specific behavior is not (should not be) tolerated. Conversely, "concerns about the code of conduct" is what we are now discussing, with CEPC being written in such a way that defeats its stated purpose. |
I think that "reporting" and "what to do if you made a mistake" should be different sections... It would be helpful to give more substance to the "reporting" - include directly telling someone about the problem, reporting an apparent pattern of behaviour because there are different implications to a simple atypical mistake, ... |
@vlevantovsky I chose to phrase it as "concerns" instead of "violations" because it is gentler language. We want to encourage people with any concerns, even if they think it is not a full-blown "violation" to step forward. What do you think? |
Thanks @chaals. I will make some changes. |
made "if you've made a mistake" an h2
@chaals "Reporting" is covered in the Procedures doc, which is now at https://github.com/w3c/PWETF/blob/master/PWE.html. Please make comments and propose edits there. |
@TzviyaSiegman, in my initial comment I specifically stated exactly what I think. To my ear, "violations of CEPC" has a very different meaning compared to "concerns about CEPC". |
@vlevantovsky If I'm reading this accurately (please let me know if I'm misinterpreting) you are expressing two, not necessarily connected concerns here.
|
@RachelComerford, reversing the order of topics covered:
|
Thanks @vlevantovsky! I'll maintain your order for the sake of clarity for those following.
About removing the "never" statements - I don't really see anyone here articulating that this would be an issue. In order to remove them or revise them, someone first needs to call them out individually and suggest rewrites. Now that you've identified something that you find problematic for you - are you willing to contribute to constructing the solution?
Whether we write 'violations of code conduct' or 'concerns about [potential violations of] the code of conduct' won't change that, nor will it make it more or less clear cut if there is an actual violation. Using 'Concerns' merely gives less confident users a platform for exploring their issues. |
@RachelComerford, keeping the same order
|
Wonderful! so, for (2) perhaps we have a compromise. @TzviyaSiegman are you okay with: "concerns about potential violations of the code of conduct"? |
For concern (1) - I think this needs it's own issue since this issue is a pull request for adding reporting and what to do and we (may?) have found a solution to the issue with that specific topic. I can move this information over to a new issue that doesn't block this PR. |
Thanks for the great discussion. Please note that the CEPC as proposed here is not a complete edit. This PR is about the "reporting" and "what to do" sections. There are multiple PRs and more to come. Including too many changes in one PR tends to clutter an issue and create merge conflicts. Please feel free to create a separate PR for the "never" issue which is in the Code section. |
Reason for this change: Many members and chairs have requested clearer information in the CEPC about how to respond when there is a CEPC violation. Group chairs who are not yet at the stage of involving an ombuddy have requested guidance, and "if you make a mistake" offers that guidance. |
Ah sorry this slipped my notice. I am happy you adapted the Immersive Web CoC. Re. concerns vs violations I think that is sensible. Code of conduct snafus can often be unclear and be different based on the judgement of the witnesses, victim and perpetrator. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
index.html
Outdated
|
||
<p>Alice: “Yeah I used X and it was really crazy!” Eve: “Hey, could you not use that word? What about ‘ridiculous’ instead?” Alice: “oh sorry, sure.” -> edits old message to say “Yeah I used X and it was really confusing!”</p> | ||
<p>This will allow conversation to quickly continue without any need of further action or escalating the situation.</p> | ||
<p>If you don't understand what you did wrong, assume the the hurt party has good cause and accept it. We cannot know everyone's background and should do our best to avoid harm. You are welcome to discuss it with the ombuddy later.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/ombuddy/Ombudperson
I'm pretty sure we discussed the term "ombuddy" but there's no issue open for adopting it, and for consistency we should use same term throughout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed to use ombudsperson in formal documentation
minor edits based on 4/4/19 and discussion in PR
Preview | Diff