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

Annual updation of OWNERS_ALIASES #49273

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

divya-mohan0209
Copy link
Contributor

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:

  • We recognize that GitHub isn't the only way to contribute and are seeking confirmation of your intent to continue as an approver/reviewer for the next year based on your bandwidth.
  • While we understand that localisations have a different volume of contributors and contributions, the respective approvers & reviewers are expected to grow a community around every translation. If you face challenges in this aspect, please make sure you bring it up in the appropriate forum for awareness and seek assistance (e.g. slack channel, routine meetings etc) cc: @seokho-son @a-mccarthy
  • Failure to confirm your intent within the lazy consensus timeframe will cause removal from the OWNERS_ALIASES file.

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

 maintainers prune --repository-devstats "kubernetes/website" --repository-github "kubernetes/website" --dryrun=true
Running script : 01-02-2025 10:21:44
Processed /Users/divyamohan/website/OWNERS
Processed /Users/divyamohan/website/OWNERS_ALIASES
Found 44 unique aliases
Found 110 unique users
..............................................................................................................................................................

>>>>> Missing Contributions in kubernetes/website (devstats == 0): 15
Babapool
IanColdwater
ariscahyadi
bishal7679
cji
danninov
devlware
gochist
idvoretskyi
jmyung
joelsmith
jrsapi
mattiaperi
yoonian
ysyukr


>>>>> Low reviews/approvals in kubernetes/website (GH pr comments <= 10 && devstats <=20): 29
Fale
SaranBalaji90
SataQiu
Sea-n
Verolop
ameukam
cjcullen
fabriziopandini
girikuncoro
huynguyennovem
jcjesus
jeremyrickard
jimangel
jossemarGT
justaugustus
kakts
kinzhi
kpucynski
mfilocha
micahhausler
mickeyboxell
mrbobbytables
nvtkaszpir
palnabarun
rajibmitra
rekcah78
remyleone
rlenferink
tanjunchen
--dryrun is set to true, will skip updating OWNERS and OWNER_ALIASES%   

cc: @natalisucks @reylejano @katcosgrove @tengqm @salaxander

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from divya-mohan0209. For more information see the Kubernetes Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot requested a review from reylejano January 2, 2025 05:36
@k8s-ci-robot k8s-ci-robot added the sig/docs Categorizes an issue or PR as relevant to SIG Docs. label Jan 2, 2025
@k8s-ci-robot k8s-ci-robot requested a review from sftim January 2, 2025 05:36
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 2, 2025
@divya-mohan0209 divya-mohan0209 changed the title Annual pruning exercise of OWNERS_ALIASES Annual updation of OWNERS_ALIASES Jan 2, 2025
Copy link

netlify bot commented Jan 2, 2025

Pull request preview available for checking

Name Link
🔨 Latest commit ea41589
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/677625f29a0eb60008a5d03d
😎 Deploy Preview https://deploy-preview-49273--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@rekcah78
Copy link
Contributor

rekcah78 commented Jan 2, 2025

I would like to continue contributing and approving/reviewing PRs for the FR translation

@Fale
Copy link
Member

Fale commented Jan 2, 2025

I would like to continue contributing and approving/reviewing PRs for the IT translation

1 similar comment
@remyleone
Copy link
Contributor

I would like to continue contributing and approving/reviewing PRs for the IT translation

@kakts
Copy link
Member

kakts commented Jan 2, 2025

I would like to continue contributing and approving/reviewing PRs for the JP translation

@SataQiu
Copy link
Member

SataQiu commented Jan 2, 2025

I would like to continue contributing and approving/reviewing PRs for the ZH translation

@seokho-son
Copy link
Member

Hi @divya-mohan0209

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)
This opinion is shared on behalf of the Korean team. Is it acceptable? Thanks! :)

@Sea-n
Copy link
Member

Sea-n commented Jan 2, 2025

Thanks for the reminder!
I’ve been busy with other things, so it’s fine to remove me from the list.

When I have more time to contribute to the Kubernetes community, I’ll apply for the role again. 😊

@cji
Copy link
Member

cji commented Jan 2, 2025

Hello! @micahhausler and I are both still committee-security-response members and I believe we require this role for helping with security issues as necessary (#36933)

@sftim
Copy link
Contributor

sftim commented Jan 2, 2025

Good news @cji; the tool has mentioned you, but we have no plans to remove your access.
You remain able to review and approve changes within https://kubernetes.io/docs/reference/issues-security/

@jossemarGT
Copy link

Hi, I'd like to continue contributing/reviewing to the Spanish (ES) localizations. cc @ramrodo @electrocucaracha @krol3

@kpucynski
Copy link
Member

I would like to continue contributing and approving/reviewing PRs for the PL translation

@mattiaperi
Copy link

I would like to continue contributing and approving/reviewing PRs for the IT translation

@yoonian
Copy link
Contributor

yoonian commented Jan 6, 2025

I would like to continue contributing and approving/reviewing PRs for the KR translation.

@girikuncoro
Copy link
Contributor

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

@ariscahyadi
Copy link
Contributor

I would like to continue contributing and reviewing/approving PRs for ID translation together with @girikuncoro

@mfilocha
Copy link
Contributor

mfilocha commented Jan 7, 2025

I will contribute to Polish (PL) localization along with @nvtkaszpir .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.