[coc-incident-resolution-ombuds] Confidentiality and Privacy
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 84
- Forks
- 69
- Avg merge
- 14h 52m
- Merged PRs (30d)
- 2
Description
Referencing https://github.com/w3c/guide/blob/main/process/coc-incident-resolution-ombuds.md ...
The procedures should more clearly address questions and concerns regarding confidentiality and privacy:
- Those receiving a confidential report should not reveal details that would expose a victim of abuse to increased harassment--while balancing the need for impartiality and due process by allowing the accused to know and address any unsubstantiated allegations against them.
- It should be made clear whether private communications (e.g. 1:1 emails, DMs) that constitute part of the problematic behavior being reported may be disclosed as part of the incident investigation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading coc-incident-resolution-ombuds.md and the related discussion in issue 334. Update the procedures to address protecting victims' confidentiality while preserving impartiality and due process, and clarify whether private communications involved in reported behavior may be disclosed during an investigation; done means both questions are explicitly addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100