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
Proposing self as maintainer #1889
Comments
+1 - very supportive of this move. |
+1 I just removed myself from codeowners and hope you hot swap in with this :) |
As a community member, I am also in favor of this. |
haydentherapper
added a commit
to haydentherapper/community
that referenced
this issue
Dec 11, 2023
Fixes sigstore/rekor#1889 Signed-off-by: Hayden Blauzvern <hblauzvern@google.com>
+1 |
bobcallaway
pushed a commit
to sigstore/community
that referenced
this issue
Dec 12, 2023
Fixes sigstore/rekor#1889 Signed-off-by: Hayden Blauzvern <hblauzvern@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I'd like to propose myself as a maintainer for Rekor. I'm active in the development of Rekor, both as a service and library, and the developer of a Rekor log monitor. I am active in the transparency ecosystem, focused on implementing log verification through witnessing and stronger offline verification for clients, so well-versed in how to maintain a transparency log.
Substantial PRs include:
I've also been an active code reviewer for a couple of years and have had the permission to approve PRs (but not merge) since February.
cc codeowners for +1s: @priyawadhwa @bobcallaway @asraa @lukehinds
The text was updated successfully, but these errors were encountered: