Issue 247 - Draft guidelines for forum moderation#248
Issue 247 - Draft guidelines for forum moderation#248dbooth-boston wants to merge 4 commits intow3c:mainfrom
Conversation
There was a problem hiding this comment.
We need to explain clearly the policy in relation to editing or deleting posts on a list, which go in two directions:
- How to handle the situation when a deletion or edit is itself a violation of the CPC.
- The circumstances in which addressing a violation should/must/must not include editing or deleting a post, and who has the responsibility for doing that.
|
This document talks specifically about email lists, but much discussion in W3C groups today happens in GitHub issues, so I suggest bringing that in scope. |
ListModeration.md
Outdated
|
|
||
| Main responsibilities: | ||
| - Follow all posted content, at least enough to notice whether any content violates W3C policies. | ||
| - Ensure that list participants abide by the [W3C Code of Professional Conduct](https://www.w3.org/Consortium/cepc/) (CPC). The enforcement approach should depend on the circumstances: |
There was a problem hiding this comment.
CEPC, unless/until we decide to change name.
There was a problem hiding this comment.
Done in the latest version.
I think this is now addressed in the latest version, because the latest version now refers broadly to "any suspected violation" of the CEPC.
Based on feedback during the 14-Mar-2023 meeting, guidance on addressing a violation was removed and instead the document points to https://github.com/w3c/PWETF/blob/main/DisputeResolution.md for guidance on handling it. |
Done in the latest version. |
ForumModeration.md
Outdated
|
|
||
| Other responsibilities: | ||
| - Follow all posted content, at least enough to notice whether any content violates W3C policies. | ||
| - Ensure that list participants abide by the [W3C Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/) (CEPC). |
There was a problem hiding this comment.
I suggest removing "list" here, it seems unnecessary, and not always applicable, e.g., when not a mailing list.
There was a problem hiding this comment.
Good point. I've made that change in the latest version.
This addresses #247