CoC: Provide additional guidelines for in-person reports
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the discussion in Marissa's comment on typelevel/governance#129 and review the repository's existing Code of Conduct guidance. Add written guidance covering how reports should be handled in in-person or real-time situations; done when those scenarios and follow-up steps are documented.
Written by the indexing model from the issue text.
Description
Capturing follow up work from discussion stemming from Marissa's comment here
In-person/real-time scenarios aren't unlikely to come up, so it would be good to have some written guidelines for working with CoC reports in those situations as well
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from typelevel/foundation
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
typelevel/foundation#8 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
typelevel/foundation#7 · 2 comments ·
All issues in typelevel/foundation
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·