Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix and unify language of in-app messages #15458

Closed
rkratky opened this issue Dec 11, 2019 · 1 comment
Closed

Fix and unify language of in-app messages #15458

rkratky opened this issue Dec 11, 2019 · 1 comment
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@rkratky
Copy link

rkratky commented Dec 11, 2019

Is your task related to a problem? Please describe.

The language (and formatting) of in-app messages and GUI elements is often not correct (English), inconsistent within the app, or not consistent with industry standards.

Describe the solution you'd like

  • Do a sweep to fix offenders.
  • Prepare a terminology glossary to serve as a reference for developers & writers.
  • Start doing regular reviews of feature PRs that touch this content.

Additional context

  • Need to identify which components contain in-app messages.
@rkratky rkratky added kind/task Internal things, technical debt, and to-do tasks to be performed. team/doc labels Dec 11, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 11, 2019
@benoitf benoitf added area/doc Issues related to documentation severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 11, 2019
@che-bot
Copy link
Contributor

che-bot commented Jun 11, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 11, 2020
@che-bot che-bot closed this as completed Jul 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants