nextcloud / nextcloud/cookbook
Rephrase error messages
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 641
- Forks
- 113
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 26
Description
All (user facing) error messages should be revisited and checked for clarity. There should be no overly technical messages there that are shown to the user directly.
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
The issue names no files, tests, or entry points; begin by locating the cookbook's user-facing error messages. Review the full set for overly technical wording and consider the work done only when all such messages have been made clear to users.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100