Skip to content
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

Add process for handling reports #271

Merged
merged 30 commits into from
Sep 23, 2019
Merged
Changes from 1 commit
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
de67a3e
Add process for handling reports
keywordnew Jul 23, 2019
3a41881
Combine report handling with S1 CoC proposal
keywordnew Jul 30, 2019
0fe421d
Address comment: specify subject of reports
keywordnew Jul 30, 2019
fbbf763
Add need to review personal info storage on Github
keywordnew Jul 30, 2019
e3bf6ef
Address comment: explicitly list collecting opinions
keywordnew Jul 30, 2019
dac1d84
Address comment: allow for issues to be closed in certain conditions
keywordnew Jul 30, 2019
b9b2131
Add CPC as role
keywordnew Aug 7, 2019
25d3fd2
Add TBD: role of members
keywordnew Aug 7, 2019
e996830
Apply suggestions from review
keywordnew Sep 3, 2019
516f586
Update placeholder email
keywordnew Sep 5, 2019
b3f81e8
Use suggestions
keywordnew Sep 5, 2019
16e4431
Update README.md
keywordnew Sep 5, 2019
3e0d1a9
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 6, 2019
f547434
squash: align with rest of docs in proposal
mhdawson Sep 6, 2019
1d5aaf2
squash: fix typos
mhdawson Sep 6, 2019
2eef5ce
squash: fix email for coc-escalation
mhdawson Sep 6, 2019
98902f7
squash: fixup
mhdawson Sep 6, 2019
bd5837b
squash: add ref about members recusing themselves
mhdawson Sep 6, 2019
366444e
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 10, 2019
9671542
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 10, 2019
377b53e
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 10, 2019
6d12e32
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 10, 2019
37c2999
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 10, 2019
d475032
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 10, 2019
84e9406
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 10, 2019
f575cec
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 10, 2019
d84e0d3
squash: Address @kborchers comments
mhdawson Sep 10, 2019
a58aa13
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 12, 2019
20ea625
squash: address comments from @mcollina
mhdawson Sep 12, 2019
d72c623
Update proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
mhdawson Sep 17, 2019
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add need to review personal info storage on Github
keywordnew committed Jul 30, 2019
commit fbbf76341d6a9ecf3308b245a67ecd2f1ddcbaae
10 changes: 4 additions & 6 deletions proposals/stage-1/CODE_OF_CONDUCT/HANDLING-REPORTS.md
Original file line number Diff line number Diff line change
@@ -4,12 +4,10 @@ This document describes the proposed process for handling reports and escalation
Reporting to the OpenJS Foundation either concerns a matter with the Foundation or is considered an escalation where insufficient resolution was provided by a project, with regards to violations of the Code of Conduct.

## Channels
* Email: report@openjsf.org
* This email address is for aliasing (like tsc@nodejs.org) to roles in handling reports and escalation.
* We can use groups.io
* Form: It would be easier on the reportee to have a form template to help them structure their report. The form submission could trigger an email
* Repo: openjs/moderation (not provisioned)
* A form submission could open an issue in the repo, to allow folks to discuss in context
* Email: report@openjsf.org.
* Form: It would be easier on the reportee to have a form template to help them structure their report. The form submission could trigger an email.
keywordnew marked this conversation as resolved.
Show resolved Hide resolved
* Repo: openjs/moderation (not provisioned). As commented in PR review, hosting sensitive personal information on GitHub needs due consideration, review, and possibly legal consultation.
Copy link
Contributor

Choose a reason for hiding this comment

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

similar to above. This document should outline the actual process rather than questions about process.

Also, is this document for project maintainers or external individuals? That would likely change the process a bit.

Copy link
Member Author

Choose a reason for hiding this comment

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

This document was written initially for project maintainers.

Removing content to README.md. Thanks for calling out.

* A form submission could open an issue in the repo, to allow folks to discuss in context.
keywordnew marked this conversation as resolved.
Show resolved Hide resolved
## Confidentiality and record-keeping
Everything reported and discussed is confidential unless explicitly stated. For any facts to be made public, the reportee’s explicit permission is needed. All reports should be recorded, together with the discussion of it. A private moderation repo would satisfy the need for recordkeeping.
Copy link
Contributor

Choose a reason for hiding this comment

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

For any facts to be made public, the reportee’s explicit permission is needed.

Are we sure we want to commit to this? If we want to make even anonymized summaries of reports / actions taken that will not be possible with the current reading.

mhdawson marked this conversation as resolved.
Show resolved Hide resolved
## Steps/Escalation