Test translation tooling for localizations about website HOT 37 OPEN

I am ready to participate as part of the Ukrainian localization team 🇺🇦.

I have already given examples of using Crowdin and Transifex in #45209, if you put them in a pile, we get the following

I hope this is helpful and will speed up the platform selection process.

from website.

Hi @a-mccarthy, could you please also add @edsoncelio to the group of interested people in pt-br? 🙏🏻 I mentioned in my original comment but I guess it got lost 😅

from website.

I would like to volunteer as a TLMP tester and localization reviewer for German (and could help with Brazilian Portuguese also if needed).

from website.

I'd like to volunteer for the role of TLMP administrator.
To improve response times, we should prefer administrators in differing time zones.

from website.

I'd like to volunteer as a TLMP tester for pt-br.

from website.

@stormqueen1990, added! apologies @edsoncelio 🙏

from website.

Hello! Friendly neighborhood CNCF rep here. <3

1. POC work is fine, but before we (CNCF) need to review the Terms of Service for CrowdIn before too much happens (I'll kick this off, don't block on this)
2. When you say unlimited open source license, is there any time box or additional info beyond what's on the OSS License Request? -- Relatedly, should we fill this out or were we hand-waving this for the POC work?
3. If this really takes off, would love to talk about a partnership for the rest of the CNCF projects 😍

Thanks! Loop me into the Slack channel as well in case any quick questions arise. :D

from website.

@natalisucks @jeefy I've joined #sig-docs-localizations 🤞 fingers crossed I can be of help

from website.

I am ready to participate as part of the Ukrainian localization team 🇺🇦.

from website.

@edsoncelio and I, from the Brazilian Portuguese localization team, are interested in volunteering for this. We do have one outstanding question: is it mandatory that all the involved people in the localization be at least a reviewer?

from website.

I want to volunteer for Korean TLMP tester and Localization reviewer. After other Korean volunteers choose their roles, I will choose the remaining seat between them.
And I (or someone else) might ask more person to involve, at K8s Slack Korean L10n channel.

from website.

Transferred my comment here to #45209 (comment) , in favor of Tim's comment.

from website.

The best place to suggest or discuss which tool we might use is: #45209

from website.

I want to like to volunteer as a TLMP tester and localization reviewer for Arabic (and I can also help with French also if needed).

from website.

Hello everyone,

Serhiy from Crowdin

I was super happy to find this discussion! I just wanted to say that we're more than happy to issue an unlimited open source license for this project and support you as much as we can. I would need your Crowdin login or an organization name to issue a license.

I also wanted to suggest a Slack channel for quick communication with Crowdin, especially during the setup period. Please let me know if this would be helpful.

from website.

We would welcome every single CNCF project with open arms!

is there any time box or additional info beyond what's on the

No, no restrictions on open source. We only need your Crowdin.com login to create a license on our end.

If this really takes off, would love to talk about a partnership for the rest of the CNCF projects 😍

I started a Slack channel and sent an invitation (probably to your personal email address 😬).

I want to recommend a quick call with our architects before the POC to make sure the experiment goes smoothly.

from website.

Hi! I'd like to volunteer as a TLMP tester/localization reviewer for Russian.

from website.

I've stepped back as a technical lead for the SIG; I'm willing anyway to help informally with this work.

from website.

I am ready to participate as part of the Ukrainian localization team 🇺🇦.

from website.

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from website.

@sftim and @seokho-son

from website.

I can cover the technical lead participation.

from website.

is it mandatory that all the involved people in the localization be at least a reviewer?

@stormqueen1990 no, its not required ALL the members of a localization participate, but it would certainly be helpful to get to opinion of multiple people within a team. We are asking that there are at least 2 reviewers from one team and at least one contributor who's not a reviewer. So i think that works out to needing 3 or 4 people from one team who are able to contribute to the testing as either a reviewer or a contributor.

from website.

• Use cases/workflows tested
• Tooling implementation requirements
• Long term support requirements

Team,

I'm looking to enhance our project planning and info gathering on key areas like use cases, tooling requirements, and long-term support. My plan is to set up Crowdin and Transifex accounts for better preparation and insight.

Unless there are objections, I’ll get started on this soon. Thoughts?

from website.

My plan is to set up Crowdin and Transifex accounts for better preparation and insight.

Unless there are objections, I’ll get started on this soon. Thoughts?

We should try to set up a Google Group to represent Kubernetes as owner of the SaaS tenancies there. Also, let's not actually start until we've confirmed we're kicking off the work and have resources in place.

from website.

/lifecycle active

from website.

We should try to set up a Google Group to represent Kubernetes as owner of the SaaS tenancies there.

Should I (or one of us) simply create the group, or would it be better to have someone with an "official" kubernetes.io-related email address do that?

from website.

Also, let's not actually start until we've confirmed we're kicking off the work and have resources in place.

I'll hold off on creating the account that we use for this project.
What's the current timeline, or what next steps do we need to complete before kicking off the project?

from website.

is it mandatory that all the involved people in the localization be at least a reviewer?

@stormqueen1990 no, its not required ALL the members of a localization participate, but it would certainly be helpful to get to opinion of multiple people within a team. We are asking that there are at least 2 reviewers from one team and at least one contributor who's not a reviewer. So i think that works out to needing 3 or 4 people from one team who are able to contribute to the testing as either a reviewer or a contributor.

Amazing! I think Brazilian Portuguese might be at (or close to) quorum then 🙂

from website.

Thank you all for your interest! I was planning to volunteer as comms lead as well.

Ideally we'd have 2 languages with a full set of testers (3 or 4 people). So far we have the following volunteers:

pt-br: @stormqueen1990, @zilmarr, @holgers66, @edsoncelio
ar: @seifrajhi
ko: @jihoon-seo
uk: @Andygol

Other volunteers:
TMPL admins: @rolfedh (needs 1 volunteer)
Tech lead: @sftim
comms lead: @a-mccarthy

If you would like to participate, please respond by Monday, April 22nd with your interest. If we are able to fill the volunteer positions, then we can start planning for a testing kick off date and the timelines within the testing window (about 1 month from the kickoff date).

from website.

Hi @dies 👋 thank you for reaching out. Great to hear about the open source license, once we have staffed the roles and decided to move forward we can chat more about setting that up.

I also wanted to suggest a Slack channel for quick communication with Crowdin, especially during the setup period. Please let me know if this would be helpful.

Do you mean a slack channel on a Crowdin slack? or some place else?

from website.

Yes, a channel in our Slack where we can have our customer care team and engineers if needed and all the people involved from your side (project/community managers, engineers that might have technical questions)

from website.

@natalisucks @sftim Does it make sense to direct folks, initially, to #sig-docs or perhaps #sig-docs-tools in the Kubernetes slack? Ignoring my pie-in-the-sky thoughts for other projects, this started as a Kubernetes initiative so I want to scope it that way and direct @dies and co to the right place.

from website.

@jeefy Thanks for thinking about this, the best channel for this initiative, as agreed by @a-mccarthy and other leads of this work, will be #sig-docs-localizations. Given we'll have several localization teams involved in this test, we want to keep the radius of this work wide enough for them, but concentrated outside of larger SIG Docs channels. Thanks!

from website.

Hi! I'd like to volunteer as a TLMP tester/localization reviewer for Russian.

from website.

Hi folks! I'd like to volunteer as a TLMP Tester/Localization Reviewer for Hindi.

from website.

Hi @a-mccarthy, I hope you're doing well. I wanted to check in on the current status of resourcing for the TLMP testing project. Could you provide an update on when we might expect the official go-ahead? Your guidance will be greatly appreciated as we plan our contributions. Thanks!

from website.