REQUEST: New membership for mengjiao-liu

[mengjiao-liu]

GitHub Username

@mengjiao-liu

Organization you are requesting membership in

@kubernetes

Requirements

• I have reviewed the community membership guidelines (https://git.k8s.io/community/community-membership.md)
• I have enabled 2FA on my GitHub account (https://github.com/settings/security)
• I have subscribed to the kubernetes-dev e-mail list (https://groups.google.com/forum/#!forum/kubernetes-dev)
• I am actively contributing to 1 or more Kubernetes subprojects
• I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

• @ehashman
• @neolit123

List of contributions to the Kubernetes project

• PRs reviewed / authored
  https://github.com/kubernetes/kubernetes/pulls?q=is%3Apr+author%3Amengjiao-liu
  https://github.com/kubernetes/community/pulls?q=is%3Apr+author%3Amengjiao-liu+
  fix kubelet --logging-format flag line feed is incorrect kubernetes#100165
  kubectl default container behavior kubernetes#99833
  Move Logs options to component-base/config kubernetes#99693
  modify the TestController2_updateCronJob test method description kubernetes#99614
  update kubectl cp flag description kubernetes#99581
  Migrate pkg/kubelet/lifecycle,oom to structured logging kubernetes#99479
  Clarify external CSR signerName field description kubernetes#99444
  remove unused code associated with volume kubernetes#99301
  fix VolumeMount permissions with subpaths only apply the right permsions to the last directory kubernetes#98717
  Update contributors development.md community#5461

• Issues responded to
  https://github.com/kubernetes/kubernetes/issues?q=is%3Aissue+author%3Amengjiao-liu+
  kubelet --logging-format flag wrap the description incorrectly kubernetes#100130
  Volumes accept anything as volume type without complaining, and defaults to emptyDir kubernetes#93719
  Failed to run the pod with duplicate persistent volumes kubernetes#99453

• SIG projects I am involved with
  COSI related
  https://github.com/kubernetes-sigs/container-object-storage-interface-provisioner-sidecar
  https://github.com/kubernetes-sigs/container-object-storage-interface-controller
  https://github.com/kubernetes-sigs/container-object-storage-interface-csi-adapter
  Add deployment documentation kubernetes-retired/container-object-storage-interface-csi-adapter#22
  Add deployment documentation kubernetes-retired/container-object-storage-interface-controller#38
  Add Deployment documentation kubernetes-retired/container-object-storage-interface-provisioner-sidecar#37

[neolit123]

thank you for the contributions @mengjiao-liu
+1

[ehashman]

👍 welcome!

[nikhita]

@mengjiao-liu thank you for all your contributions so far \o/

I've created PR #2579 to add you to the Kubernetes Org. Once that gets merged, you should get a membership invite notification.

Welcome to @kubernetes! 🎉

/assign

[wlan0]

Hi @nikhita!

Does this grant @mengjiao-liu merge privileges on the COSI projects?

I'm asking because I've never talked to this person, and their involvement with COSI projects is a bunch of unmerged docs PRs. While I really appreciate their contribution and would be happy to facilitate their path towards approvership, I'm not sure if someone who isn't involved with the COSI community at all should be getting merge privileges, atleast not yet. Not to mention, they are new to the kubernetes org as well.

[ehashman]

👋 @wlan0

per https://github.com/kubernetes/community/blob/master/community-membership.md#member members' privileges are:

Members are continuously active contributors in the community. They can have issues and PRs assigned to them, participate in SIGs through GitHub teams, and pre-submit tests are automatically run for their PRs.

Merge rights are granted via addition to OWNERS files. Being an org member for at least three months is a prerequisite to become a reviewer. An approver (who has merge rights) must be a reviewer for at least three months.

[wlan0]

Thanks, that makes sense

[mengjiao-liu]

To clarify, I did not apply for COSI member @wlan0

[wlan0]

Got it @mengjiao-liu! Thanks for confirming. That being clarified, I do really appreciate your contributions and I’d be happy to work with you and get you approver/reviewer privileges as you make more of them :-)

[mengjiao-liu]

Thanks. I will devote more time to the COSI project.