Call-for-Code-for-Racial-Justice / Call-for-Code-for-Racial-Justice/TakeTwo
Investigate & document other efforts around abusive language, toxic language, etc.
- Dominant language
- No language data
- Stars
- 27
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
### Background on the problem the feature will solve/improved user experience
Since beginning the project, we've come across many similar efforts around mitigating racially biased language and toxic language identification. Documenting similar efforts could help us identify opportunities for collaboration and learn from other solutions.
### Describe the solution you'd like
Documentation on what similar projects are out there, how TakeTwo is similar, and how TakeTwo is different, and what lessons learned can we use from these similar solutions.
### Tasks
Investigation and documentation of similar projects
### Acceptance Criteria
See above.
Contributor guide
Research direction
The issue body is the only entry point mentioned; start by investigating similar efforts addressing abusive, toxic, or racially biased language. Done means documenting comparable projects, explaining how TakeTwo is similar and different, and recording lessons that could support collaboration or improve its solution.
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