letsencrypt / letsencrypt/cp-cps
Clean up use of "sensitive data"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 38
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Although we don't capitalize "sensitive data" and don't use that phrase as a Defined Term, we do have an internal definition for that same term that doesn't exactly match how it is used in our CP/CPS. It would be cleaner to use a different phrase here, to prevent any confusion for readers who are familiar with the internal definition.
Contributor guide
No contributing guide indexed for this repository
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 CP/CPS documents for uses of “sensitive data” and compare each occurrence with the internal definition and the current CP/CPS usage. Confirm the intended replacement wording with a maintainer, then update the affected document text and verify that the phrase no longer creates confusion.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100