Add erikgb as maintainer

[inteon]

Erik (@erikgb) has been an important contributor to cert-manager and more specifically trust-manager.

• The improvements Erik has made to trust-manager have improved the project's usefulness and correctness (he has both contributed directly through PRs and indirectly by reviewing PRs).
• Erik also contributed to other controllers like approver-policy and cert-manager.
• He has been joining a lot of our stand-ups and is a trustworthy contributor.

Adding Erik as a maintainer will diversify our maintainers team and it will allow us to give him admin privileges on the trust-manager project, so he can cut releases of trust-manager when required (see https://github.com/cert-manager/community/blob/main/GOVERNANCE.md for requirements wrt. admins).

I (@inteon) think @erikgb is an important part of our community and for that reason must receive the privileges required to contribute optimally. I would trust @erikgb with more admin privileges, but think it is better to restrict his privileges to the actions he is interested in (in case of compromise of his account), additionally this will reduce the scope of the perceived responsibilities that come with these privileges (both for Erik and the rest of the community, eg. no one will ping him to do a cert-manager release).

I'd like us to approve this appointment using lazy consensus:

🧑‍💻 Participants: @cert-manager-maintainers
📢 Deadline: July 19th, 2024 23:59 UTC
🚨 Note: to speed up the process, you may answer with a 👍 or a comment stating that you are lazy to help reach consensus before the deadline.

[SgtCoDFish]

Erik has been the MVP of the cert-manager community for a long time. He's active in meetings, highly knowledgable, and a good person to chat to.

I fully support his nomination and I fully support this proposal 👍

[inteon]

NOTE: this vote has been accepted.

I'm on holiday right now, so I won't be able to make the administrative changes until I'm back. Other maintainers might be able to make them sooner.

[SgtCoDFish]

Erik is also on holiday at the moment, so there's no great rush on this!

[maelvls]

Pre-Onboarding Checklist — info to be requested to the new maintainer:

• New maintainer's email: ...
• New maintainer's GitHub ID: @erikgb
• New maintainer's Kubernetes Slack ID (see here for how to get it): ...

Onboarding Checklist — tasks to be performed by an existing maintainer:

Onboarding Maintainer: @inteon

Don't forget to add the links to the various PRs or IT tickets as you complete the tasks, and add any missing item.

Initial Privileges:

• Add new maintainer's email to project-maintainers.csv. - see Add Erik Godding Boye as a cert-manager maintainer cncf/foundation#844
• Add new maintainer's GitHub ID as member of milestone-maintainers.
• Add new maintainer's Kubernetes Slack ID to the @cert-manager-maintainers group (see this example). - see Add new cert-manager maintainer erikgb to the slack usergroup kubernetes/community#8068
• Add new maintainer's email to cert-manager-security@googlegroups.com
• Add new maintainer's email to cert-manager-maintainers@googlegroups.com
• Request CNCF service desk to add new maintainer's email to the CNCF mailing list cncf-cert-manager-maintainers. - see https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-2437
  • Once the above request has been processed, ask the new maintainer to send an email to cncf-maintainer-changes@cncf.io with their info (email, git ID, and name) to get invited to the CNCF service desk. - email was sent

Self-access Privileges:

• Go over the list of self-service privileges the new maintainer can get access to by showing them the infrastructure README. Let them know that they can admin access to any of these services by opening a ticket at servicedesk.cncf.io.

Privileges added outside of the CNCF Service Desk:

These are the list of privileges that weren't asked through a ticket at servicedesk.cncf.io because this service isn't owned by the CNCF yet.

• Add @erikgb to approver-policy-maintainers and trust-manager-maintainers (see https://github.com/cert-manager/org/pull/1/files#diff-782d8a7f2fd016126c61cc73689fb5d7480f3ec3f140f2872e8a56fe8c4344e2R75-R87)

[maelvls]

@inteon Thanks for taking care of the onboarding checklist. Feel free to edit the checklist message above with your progress (PR link, etc) sor any additional steps that isn't in the list.

[maelvls]

Not sure why this PR hasn't been merged yet 😅

The lazy-consensus vote ended on July 19th, 2024, which means this PR can be approved.

/lgtm
/approve

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maelvls

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 [maelvls]

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