Use 'Requirement' instead of CRE
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 180
- Forks
- 137
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 21
Description
New visitors don't know what a CRE is. Besides it's common requirement ENUMERATION. So it should in fact read CR. Let's call it Requirement everywhere. To start with at the places where we say "Which contains CREs" and "Which is related to CREs"
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
Search the repository for the phrases "Which contains CREs" and "Which is related to CREs", then inspect nearby uses of CRE. Replace the user-facing terminology with Requirement consistently and verify that the targeted wording no longer uses CRE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- content
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100