-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Annual updation of OWNERS_ALIASES #49273
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Pull request preview available for checking
To edit notification comments on pull requests, go to your Netlify site configuration. |
I would like to continue contributing and approving/reviewing PRs for the FR translation |
I would like to continue contributing and approving/reviewing PRs for the IT translation |
1 similar comment
I would like to continue contributing and approving/reviewing PRs for the IT translation |
I would like to continue contributing and approving/reviewing PRs for the JP translation |
I would like to continue contributing and approving/reviewing PRs for the ZH translation |
For Korean localization owners (sig-docs-ko-owners) and reviewers (sig-docs-ko-reviews), even if their activity was minimal or absent last year, they are contributors we may need to rely on for maintaining this year. The Korean localization will soon require extensive revisions, and we plan to separately reach out to these contributors for support. Until new owners and reviewers gradually take their place, we request that the current ones remain as they are for now. (@gochist, @jmyung, @yoonian, @ysyukr) |
Thanks for the reminder! When I have more time to contribute to the Kubernetes community, I’ll apply for the role again. 😊 |
Hello! @micahhausler and I are both still |
Good news @cji; the tool has mentioned you, but we have no plans to remove your access. |
Hi, I'd like to continue contributing/reviewing to the Spanish (ES) localizations. cc @ramrodo @electrocucaracha @krol3 |
I would like to continue contributing and approving/reviewing PRs for the PL translation |
I would like to continue contributing and approving/reviewing PRs for the IT translation |
I would like to continue contributing and approving/reviewing PRs for the KR translation. |
I would like to continue contributing and reviewing/approving PRs for ID translation, I've been busy relocating to new country but should settle down now cc @ariscahyadi |
I would like to continue contributing and reviewing/approving PRs for ID translation together with @girikuncoro |
I will contribute to Polish (PL) localization along with @nvtkaszpir . |
Context
We've been using the maintainer's tool to clean up the OWNERS_ALIASES file for k/website annually. With this exercise, we aim to keep the file updated and hope to foster healthy community leadership within SIG Docs. The results of running the tool this year have been provided below.
What do I need to do if I have been tagged on this PR?
If you wish to continue as an approver, reviewer, or localization owner, please confirm your intent on this PR by 2nd February 2025
Points to note:
Changes proposed by this PR
Pruning following folks from OWNERS_ALIASES due to zero contributions OR contributions < 25.
@Babapool
@ariscahyadi
@bishal7679
@cji
@danninov
@devlware
@gochist
@jmyung
@mattiaperi
@yoonian
@ysyukr
@Fale
@SataQiu
@Sea-n
@fabriziopandini
@girikuncoro
@huynguyennovem
@jcjesus
@jossemarGT
@kakts
@kinzhi
@kpucynski
@mfilocha
@micahhausler
@mickeyboxell
@nvtkaszpir
@rajibmitra
@rekcah78
@remyleone
@rlenferink
@tanjunchen
Output of the maintainers tool
cc: @natalisucks @reylejano @katcosgrove @tengqm @salaxander