REQUEST: Role change for Lead

[joaopapereira]

Summary

This is a formal request for consideration of a role change in the Carvel project by a member of the community.

Each role is defined in our contribution model document. If you would like to request mutliple roles / multiple
subprojects,
please open a new issue for each request.

GitHub Username

@joaopapereira

Role Requested

• Reviewer
• Approver
• Lead

Applicable Subproject

• carvel-kapp-controller
• carvel-ytt
• carvel-kapp
• carvel-kbld
• carvel-imgpkg
• carvel-vendir
• carvel-secretgen-controller
• kctrl

General Requirements

• I have reviewed the code of conduct (https://github.com/vmware-tanzu/carvel/blob/develop/CODE_OF_CONDUCT.md).
• I have enabled 2FA on my GitHub account (https://github.com/settings/security).
• I have active participation and provide support (such as GitHub, meetings, Slack, Stack Overflow) in the community
  for long enough to have demonstrated knowledge and competency (such as 3 months).
• I have at least one sponsor (
  see current maintainers list).
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application.

Role Specific Requirements

[LINK_TO_REVIEWER_DEFINITION] Reviewer

• I have reviewed / authored of at least 5 substantial* pull requests to the subproject(s).

[LINK_TO_APPROVER_DEFINITION] Approver

• I have reviewed / authored several substantial* pull requests to the codebase.
• Demonstrated the ability to plan and execute a track of work.

[LINK_TO_LEAD_DEFINITION] Approver

• I have a deep understanding of the technical goals and direction of the subproject.
• I have a deep understanding of the domains of the subproject.
• I have a deep understanding of the design of the subproject.
• I have contributed to the design and direction by doing all of:
  • Authoring and reviewing proposals.
  • Initiating, contributing and resolving discussions (emails, GitHub issues, meetings).
  • Identifying subtle or complex issues in designs and implementation PRs.
  • Directly contributed to the subproject through implementation and / or review.

Sponsors

• @pivotaljohn
• @joe-kimmel-vmw

List of contributions to the Carvel subprojects(s)

I have been an active contributor to imgpkg for the past year and a half and served as an approver for more than a
year.
During this time I was responsible for developing, roadmap, triaging, and giving support for imgpkg

PRs reviewed / authored

Currently, I authored a total of 74 PRs in the project and reviewed/approved the majority of the other PRs.
Some of the most relevant PRs are:

• Nested bundles
• Enable cosign signatures to be copied with the bundles
• Add locations image that allowed imgpkg to cache some information of the bundle in the registry
• Lower number of authentication requests needed per command
• Introduction of describe command

Issues responded to

When responding to issues I try to be proactive and better understand the problem the user is facing as well as think
about a solution and validate it with the requester.
Some examples of this are:

• Incorrect help UX on push command
• Creating bundle directly from a tar file
• Create an init command
• Creation of command to describe a bundle
• Issue with annotations

Projects I am involved with

The first project I was part of when I joined was to do a major refactor of imgpkg to better organize the code. After that
I was part of almost all the big projects of imgpkg.
Some examples of these projects are:

• Proposal and implementation of the concept of nested bundles
• Proposal with other community members to allow the users to define where images are copied to
• Proposal and implementation of first public API of imgpkg using
  the feature to check if an image is cacheable or not when pulling it
• Lower number of authentication requests needed per command
• Proposal and implementation of the describe command

Apart from the above-mentioned, you can find me in our Slack channel helping our users with questions about imgpkg and
other tools.

Vision for the tool

I see imgpkg as tool that can help standardize how software is grouped and transported from the creators to the users in a secure and timely manner.
To accomplish this I believe that we need to ensure the support for other tools to easily check bundles for CVEs, and validate the origin of the bundles.
Another area where I would like to see imgpkg grow is in its support for other projects to consume it as a library. I believe that this could unlock a wider adoption of the awesome bundle format. There are some examples, in the wild, of people interacting with imgpkg via a call to the binary, but I believe that if we provide a reacher API it would make this integration more appealing and much richer.

In terms of research, I would love to better understand how might imgpkg and the bundle format be used by other projects, like helm, to create a better experience for them.

In general, I believe, that imgpkg is positioned itself as a better way to help software creators package their software and we should try to double down on this moving forward. Some of the prior ideas are examples of how might we accomplish this.

Next Steps

• Once your sponsors have responded with a +1 for your nomination, your request will be reviewed by the project leads.
  Any missing information will be requested.

---

[pivotaljohn]

My name is @pivotaljohn and I approve this message. 😉

Seriously, tho... Joao demonstrates:

• sharp design sense through his well reasoned (and succinctly articulated) conversations (in the PRs referenced, but elsewhere as well).
• commitment to see big ideas from start through finish, given his multiple meaty (feature group sized) contributions to imgpkg ... contributions that have made this tool what it is.
• cohesive vision that extends the Carvel Intent: to make our software deeply composable, affording users the ability to integrate in the way that best works for them. He also has compelling next targets for research.

[joe-kimmel-vmw]

+1 to what's already said.

[cppforlife]

and for me as the last approver on this PR...

im +1 on @joaopapereira becoming a lead for imgpkg. he has demonstrated deep knowledge and vision in this domain.

[aaronshurley]

Merged based on previous approvals. 🎉