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.

Sign up for GitHub

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

Jump to bottom

Globalization Framework for Language Support #19900

Closed
ArvinB opened this issue Jun 1, 2021 · 8 comments
Closed

Globalization Framework for Language Support #19900

ArvinB opened this issue Jun 1, 2021 · 8 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/1-year Epics that are planned to complete in the short term (12 months or more) severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.

Comments

@ArvinB
Copy link

ArvinB commented Jun 1, 2021 •
edited
Loading

Is your enhancement related to a problem? Please describe.

Globalization strategy ensures that offering teams can consistently and efficiently deliver solutions, products, and platforms that support the language and cultural needs of our clients worldwide. Without sufficient globalization, our clients may not be able derive business value from our offerings.

Describe the solution you'd like

A framework to support internationalization / globalization for any language that can be added.

These are the 6 core languages to support at a minimum:

  • English
  • German
  • Spanish
  • French
  • Italian
  • Japanese

These are the 6 core languages to support globalization.

Describe alternatives you've considered

None, but open to ideas.

Additional context

This enhancement request is coming from IBM with a request to implement by June 1, 2022.
@ArvinB ArvinB added the kind/enhancement A feature request - must adhere to the feature request template. label Jun 1, 2021
@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 Jun 1, 2021
@tolusha
Copy link
Contributor

tolusha commented Jun 2, 2021

I think it is about providing support for internalization and allows anyone to contribute any language he wants.

@ArvinB
Copy link
Author

ArvinB commented Jun 2, 2021

@tolusha Agreed, a framework to support internationalization. Updating the title and description to reflect this.

@ArvinB ArvinB changed the title Globalization Enhancement Request Globalization Framework for Language Support Jun 2, 2021
@l0rd l0rd added severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. roadmap/1-year Epics that are planned to complete in the short term (12 months or more) and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jun 2, 2021
@l0rd
Copy link
Contributor

l0rd commented Jun 2, 2021

@ArvinB that should be decomposed in multiple (independent) subtasks, each one dedicated to the i18n of the messages/UI of one of Che components:

  • chectl
  • Che dashboard
  • Che operator
  • DevWorkspaces operator
  • Devfile and Plugin registries metadata
  • Che Theia

@sympatheticmoose I am labelling that as a roadmap/1-year epic.

@sympatheticmoose
Copy link

@ArvinB is this something which IBM are able to assist with implementing?

@ArvinB
Copy link
Author

ArvinB commented Jun 3, 2021 •
edited
Loading

@ArvinB is this something which IBM are able to assist with implementing?

@sympatheticmoose
Yes we plan on assisting with this.

Related item for Eclipse Che - Theia

@stevisco
Copy link

Isn't this the same as eclipse-theia/theia#1327 ? we at Arduino are working with Typefox to implement 1327 and there is a good amount of work done in PR eclipse-theia/theia#9538. We are hoping this PR makes some progress soon...

@azatsarynnyy
Copy link
Member

Isn't this the same as eclipse-theia/theia#1327 ?

@stevisco you're right, eclipse-theia/theia#1327 is the same but it's specific for upstream Theia.
This epic is a general one - for all Che components. See #19900 (comment)

@che-bot
Copy link
Contributor

che-bot commented Jan 17, 2022

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 Jan 17, 2022
@che-bot che-bot closed this as completed Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. roadmap/1-year Epics that are planned to complete in the short term (12 months or more) severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@l0rd @ArvinB @azatsarynnyy @tolusha @stevisco @sympatheticmoose @che-bot