The committers listed above are authorized under a signed CLA.

• ✅ login: Pratik-050 / name: Pratik Chandra Pal (7281a28, 7f5b429, d3523c5)

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Pratik-050
Once this PR has been reviewed and has the lgtm label, please assign illume for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Welcome @Pratik-050!

It looks like this is your first PR to kubernetes-sigs/headlamp 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/headlamp has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

Amazing. Thank you.

For Kubernetes jargon like Pods, kubectl and Kubernetes there's usually not a good word to translate it to. So we tend to keep them in English unless there's a well known word for it in the language.

We follow a linux kernel style of commit messages. With the context at the front followed by an action word and the rest.
Would you mind changing them to something like this?

frontend: app: i18n: Add Bengali language

Hello @illume thanks for your feedback!
I've translated the technical terms back to English (like: Kubernetes, Pods, Replicas, etc.). I'm native Bengali myself so I made sure that the translations looks good.
I've changed the commit message as well.
Will look forward for any further comments!

Thanks @Pratik-050

Now we need to find someone else who knows Bengali to review it.

I'm also a native Bengali speaker and happy to help with the review.

Just a quick question — is it necessary to include Bengali (or other regional languages) in Headlamp? Since the tool is mostly used by technically proficient users, many of whom are already comfortable with English, I’m wondering if localization is a priority here.

Hi @ChayanDass thanks for your offer to review. Much appreciated!

Any localization work done to make Headlamp and Kubernetes more accessible and comfy is welcome.

Thanks @ChayanDass! Please have a look into the PR when you're free.
Speaking of the regional languages, it's true that most of the professionals are proficient with English but some may find it more comfortable to experience the tool in their native language. You can find most of the tools in various regional languages. It's about making the tool more comfortable and accessible in the end.

@illume everything looks good , but I think some words are better without translation it's a suggestion .

Thanks @ChayanDass

Yeah, if there’s any words you think are better without a translation please let us know?

Just a reminder to rebase the branch against main when you get the chance to keep things up to date 😄

Yes sorry I've missed the conflicts, resolved them now.
@ChayanDass can you suggest which words are better without a translation then I can change them. Thanks!

Thanks @ChayanDass

Thanks! @ChayanDass I've resolved all your comments and also changed some translations that came to my sight please have a look again and let me know if you can find something else.

PR needs rebase.

@ChayanDass would you mind checking the last set of changes made?

Yeah , Sure I will verify the changes by Tommorow..

@illume, I have checked the changes, and it looks good to me ..

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale