add lampajr as member

[lampajr]

Read the guidelines for joining the Kubeflow GitHub org before opening an issue.

I confirm that

Provide 2-3 links to PRs or other contributions.

• Participated in manifests repo fixes for Kubeflow 1.9:
  • Add model registry sync script manifests#2682
  • Refactor test workflows  manifests#2693
  • Upgrade bentoml to 1.2.28 and 1.1.21 manifests#2704
  • Update kubeflow/model-registry manifests from v0.2.0-alpha manifests#2697
• Proposing test automation in this repo Setup test automation for github org tests #678
• Participating in add Model Registry doc to website website#3698
• Co-authored example add framingham-cvd-risk example examples#1091
• One of the contributor of Kubeflow Model Registry
• Created model registry example on Kserve website Add ModelRegistry custom storage intializer example kserve/website#346

List 2 existing members who are sponsoring your membership.

• @tarilabs
• @rimolive

Test your PR by running the following:

(internal-acls) alampare:github-orgs/ (add_lampajr) $ pytest test_org_yaml.py                                                                      [18:05:29]
==================================================================== test session starts =====================================================================
platform linux -- Python 3.10.14, pytest-8.2.0, pluggy-1.5.0
rootdir: /home/alampare/kubeflow/internal-acls/github-orgs
collected 1 item                                                                                                                                             

test_org_yaml.py .                                                                                                                                     [100%]

===================================================================== 1 passed in 0.15s ======================================================================

[google-oss-prow]

Hi @lampajr. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[hbelmiro]

/ok-to-test
/lgtm
I'm happy to sponsor @lampajr's membership.

[rimolive]

/lgtm

[tarilabs]

/lgtm

Thank you @lampajr for your contributions, happy to cosponsor membership

[terrytangyuan]

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: terrytangyuan

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [terrytangyuan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment