community: Code of Conduct sends incident reports to public issues
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github
- Domain
- documentation
Research direction
Read CODE_OF_CONDUCT.md lines 61–67 and .github/ISSUE_TEMPLATE/config.yml contact_links. Choose a private contact route for conduct reports, update both locations, and check that the CoC no longer directs sensitive reports to public issues while the template points reporters to the same private route.
Written by the indexing model from the issue text.
Description
Why it matters
Reporters of harassment shouldn't have to file in public. The CoC also promises privacy that the public route can't give.
Evidence
CODE_OF_CONDUCT.md:61-62tells people to report incidents by opening a GitHub issue.CODE_OF_CONDUCT.md:67promises maintainers will respect the reporter's privacy.- The repo already has private vulnerability reporting enabled, so a private channel exists for security reports but not for conduct reports.
Suggested approach
Name a private contact (a dedicated email alias, or a GitHub profile contact) for conduct reports. Keep public issues for non-sensitive concerns only. Mirror the contact in .github/ISSUE_TEMPLATE/config.yml contact_links.
Done when
The CoC names a private reporting route and no longer asks for public issues.
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 15
- Avg merge
- 16h 53m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 TMHSDigital/Free-Game-Dev-Assets
-
community marketing priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TMHSDigital/Free-Game-Dev-Assets#151 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
TMHSDigital/Free-Game-Dev-Assets#3 · 1 comment ·
Maintainers usually reply within 1 day
-
marketing priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
TMHSDigital/Free-Game-Dev-Assets#152 ·
Maintainers usually reply within 1 day
-
feature priority: medium
Difficulty 5/5 Over a week Newbie friendliness 25/100
TMHSDigital/Free-Game-Dev-Assets#144 ·
Maintainers usually reply within 1 day
-
bug documentation priority: high
Difficulty 4/5 3-5 days Newbie friendliness 48/100
TMHSDigital/Free-Game-Dev-Assets#137 ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/Free-Game-Dev-Assets
Similar issues
-
bug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vercel-labs/agent-skills#348 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
NanmiCoder/dsh-agent-teams#289 ·
Maintainers usually reply within 1 day