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

Does our website need to set up localized versions? #2801

Closed
windsonsea opened this issue May 29, 2023 · 3 comments
Closed

Does our website need to set up localized versions? #2801

windsonsea opened this issue May 29, 2023 · 3 comments

Comments

@windsonsea
Copy link
Member

windsonsea commented May 29, 2023

Desired feature or idea:

Our website doesn't have a localized version yet since its start.

Localized multi-language documentation is very helpful in promoting the participation and learning of OTel by developers from various countries. Translated documentation can better meet the needs of non-native English-speaking developers, making it easier for them to understand and use OTel. This is very important for the growth of the OTel community and its promotion worldwide.

In addition, localized documentation translation can also increase the activity of the community. By translating OTel's documentation into other languages, more people can be attracted to participate in the OTel community and contribute their own efforts. These people may be developers, users, or enthusiasts from different countries and regions, who can provide useful feedback, report problems, submit code, and share experiences, etc.

In short, localized multi-language documentation is an important strategy for the development and promotion of the OTel community. It helps attract more people to join this community, enhance communication and cooperation within the community, and further improve the OTel ecosystem.

@svrnm
Copy link
Member

svrnm commented Jun 5, 2023

Hey @windsonsea, sorry for the delay in answer, I was out of office last week:

In general we are open to have localized versions of the website. Until now it has not been a priority, since there is so much work that needs to be done and the current crew of contributors has no bandwidth for this.

We talked with @laziobird about a Chinese version in #2402 and here's what we need:

We need a critical mass of people, who are willing to help with that, to be sure that we can maintain and run this long term, since the existing maintainers are not able to help with that.

If you are willing to help with that, coordinate with @laziobird and other potential individuals who want to take ownership.

Thank you!

@chalin
Copy link
Contributor

chalin commented Jun 5, 2023

I'd suggest that we close this broadly-scoped issue. Onboarding a localization is a non-trivial affair, and will be dealing with each localization request individually.

@svrnm
Copy link
Member

svrnm commented Jun 6, 2023

closing this issue in favour of #2402

@svrnm svrnm closed this as completed Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants