Inclusive language
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 135
- PR merge metrics
- No merged PRs in 30d
Description
Can you address a couple of instances of language in the project where the wording can be made more inclusive? (example: whiltelist -> allowlist). We are trying to make the code in all LinkedIn projects more inclusive. Could you please examine whether or not these need to be updated, and make the changes? For suggested replacements see go/inclusivelanguage or google. THANK YOU!
Term | URL
-- | --
Master | https://github.com/linkedin/detext/blob/38e7b74879debd8ae5f2685367c81cc3a8aa003b/.github/workflows/python-app-py3.yml
Master | https://github.com/linkedin/detext/blob/1f91764f4adaea3655cabe6ce4c4f1ae23d2ac67/NOTICE
Master | https://github.com/linkedin/detext/blob/faa9957888a4dfbf1c15f82b2d4c8e8942c18776/notebooks/text_classification_demo.ipynb
Master | https://github.com/linkedin/detext/blob/180433fdcaf25baa4dcd7ba7212db23254565d5d/src/detext/run_detext.py
Master | https://github.com/linkedin/detext/blob/38e7b74879debd8ae5f2685367c81cc3a8aa003b/RELEASING.md
Master | https://github.com/linkedin/detext/blob/0ce996f846dc6998d1512a4160d52504bb15aff8/src/detext/model/bert/modeling.py
Master | https://github.com/linkedin/detext/blob/1f91764f4adaea3655cabe6ce4c4f1ae23d2ac67/test/resources/vocab.txt
Master | https://github.com/linkedin/detext/blob/38e7b74879debd8ae5f2685367c81cc3a8aa003b/.github/workflows/python-app-py3.yml
Master | https://github.com/linkedin/detext/blob/1f91764f4adaea3655cabe6ce4c4f1ae23d2ac67/NOTICE
Master | https://github.com/linkedin/detext/blob/faa9957888a4dfbf1c15f82b2d4c8e8942c18776/notebooks/text_classification_demo.ipynb
Master | https://github.com/linkedin/detext/blob/180433fdcaf25baa4dcd7ba7212db23254565d5d/src/detext/run_detext.py
Master | https://github.com/linkedin/detext/blob/38e7b74879debd8ae5f2685367c81cc3a8aa003b/RELEASING.md
Master | https://github.com/linkedin/detext/blob/0ce996f846dc6998d1512a4160d52504bb15aff8/src/detext/model/bert/modeling.py
Master | https://github.com/linkedin/detext/blob/1f91764f4adaea3655cabe6ce4c4f1ae23d2ac67/test/resources/vocab.txt
Slave | https://github.com/linkedin/detext/blob/1f91764f4adaea3655cabe6ce4c4f1ae23d2ac67/test/resources/vocab.txt
Slave | https://github.com/linkedin/detext/blob/1f91764f4adaea3655cabe6ce4c4f1ae23d2ac67/test/resources/vocab.txt
Ghetto | https://github.com/linkedin/detext/blob/1f91764f4adaea3655cabe6ce4c4f1ae23d2ac67/test/resources/vocab.txt
Ghetto | https://github.com/linkedin/detext/blob/1f91764f4adaea3655cabe6ce4c4f1ae23d2ac67/test/resources/vocab.txt
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.
Research direction
Review the listed occurrences in .github/workflows/python-app-py3.yml, NOTICE, notebooks/text_classification_demo.ipynb, src/detext/run_detext.py, RELEASING.md, src/detext/model/bert/modeling.py, and test/resources/vocab.txt. Start by checking each term in context and the project's suggested replacements. Done means the applicable wording is updated consistently without changing unrelated text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100