-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
167 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,93 @@ | ||
<table> | ||
<tr> | ||
<td>Full Name | ||
</td> | ||
<td>Socials/Company | ||
</td> | ||
<td>Why do you want to serve on the OpenSSF TAC? | ||
</td> | ||
</tr> | ||
<tr> | ||
<td>Christopher "CRob" Robinson | ||
</td> | ||
<td>Pronouns: He/Him | ||
<p> | ||
<br> | ||
Company: Intel | ||
<p> | ||
<p> | ||
<a href="https://github.com/SecurityCRob">GitHub</a> <p> | ||
<p> | ||
<a href="https://www.linkedin.com/in/darthcrob/">LinkedIn</a> | ||
</td> | ||
<td>Intel nominates Christopher "CRob" Robinson as a GB-appointed TAC member. CRob has been involved with the foundation since just after its inception and has been a strong community member and participant ever since. CRob leads multiple Technical Initiatives (BEST WG, Vuln Disclosure WG, Security Toolbelt, EDU.SIG) and participates in the End User WG, Governance Committee, DevRel Committee, and Public Policy Committee. For the last two years CRob has served on the TAC, and in 2023 voted by his peers to serve as the TAC's Chairperson and liaison with the Governing Board. We feel CRob sets an excellent role-model for community engagement and participation that we would like to see continued in 2024 and beyond. | ||
</td> | ||
</tr> | ||
<tr> | ||
<td>Sarah Evans | ||
</td> | ||
<td>Pronouns: She/Her | ||
<p> | ||
<p> | ||
Company: Dell | ||
<p> | ||
<p> | ||
<a href="https://github.com/sevansdell">GitHub</a> <p> | ||
<p> | ||
<a href="www.linkedin.com/in/sarah-evans-9456173">LinkedIn</a> | ||
</td> | ||
<td>I would like to serve as the GB appointed TAC member to contribute technical leadership to OSS security objectives. My current engagement with OpenSSF has primarily leveraged my business experience. I have participated as a Governing Board observer seeking to accelerate Technical Initiatives through strategic governance and operations. Accomplishing this goal required partnership with the TAC and gave me a deep appreciation for the technical leadership they provide. Appointing me to a TAC leadership role more specifically allows the OpenSSF to leverage my technical expertise. | ||
<p> | ||
I bring diverse technical and security experience to the TAC. In my current role at Dell, I perform cybersecurity innovation research for the global CTO R&D organization. I have also been an enterprise security architect for Dell’s internal security team and have held roles in Identity and Access Management and IT at Wells Fargo and the US Air Force. Balancing these experiences in large enterprises, I have also worked in regional companies with small IT teams to create security partnerships with individual software developers. | ||
<p> | ||
As a GB appointed TAC member, I will collaboratively apply both my technical security and business strategy leadership with other TAC members to accelerate technical OSS security outcomes. | ||
</td> | ||
</tr> | ||
<tr> | ||
<td>Zach Steindler | ||
</td> | ||
<td>Pronouns: He/Him | ||
<p> | ||
<p> | ||
Company: GitHub | ||
<p> | ||
<p> | ||
<a href="https://github.com/steiza">GitHub</a> <p> | ||
<p> | ||
<a href="https://www.linkedin.com/in/steiza/">LinkedIn</a> | ||
</td> | ||
<td>Zach has been an extremely engaged member of the TAC since being nominated to serve there several months ago. He's deeply committed to this problem space and wants to continue to serve. He's also demonstrated a broad ability to interact with peers across the ecosystem to drive change in a way that brings others along. I've included his statement from his application to be on the ballot for another term on the TAC. | ||
|
||
"The OpenSSF continues to drive forward the security of the open source ecosystem, but there’s plenty of work left to do. The TAC needs to continue to make the Technical Initiative (TI) process more clear and straightforward, something I experienced first-hand in helping the AI/ML Working Group (WG) get accepted at the Sandbox stage. Over the past months, I revised the Special Interest Group lifecycle process to make it more clear and straightforward, as well participated in the Operating Model Committee to standardize the lifecycle process across all TIs. In terms of concrete security capabilities, as a co-chair of the Securing Software Repositories WG I authored “Build Provenance for All Package Registries” describing how we integrated build provenance with npm and how other registries could do the same. Soon after, the WG published a proposal “Build Provenance and Code-signing for Homebrew”, which was subsequently funded by Alpha Omega and is in the process of being implemented. The WG also adopted the Repository Service for TUF project which is helping RubyGems protect its package index from malicious tampering. I’m also an active contributor to the Sigstore project. | ||
In short, I want to serve another term on the OpenSSF TAC to continue making our organization easier to understand and work with, to ensure our proposed security capabilities are easy to use with minimal burden on maintainers and consumers, and to ensure these capabilities deliver meaningful security impact in the next year." | ||
</td> | ||
</tr> | ||
<tr> | ||
<td>Bob Callaway | ||
</td> | ||
<td>Pronouns: He/Him | ||
<p> | ||
<p> | ||
Company: Google | ||
<p> | ||
<p> | ||
<a href="https://github.com/bobcallaway">GitHub</a> <p> | ||
<p> | ||
<a href="https://www.linkedin.com/in/bobcallaway/">LinkedIn</a> | ||
</td> | ||
<td>I have served on the OpenSSF TAC for the past two years (one as chair) and have worked with my colleagues on the TAC & governing board to adopt a project governance process and refined the technical vision of the foundation. We have made significant progress in 2022-2023 in evolving the identity of the OpenSSF and helped to guide the community to address the wide landscape of problems present in this space. I am nominating myself in this election as I hope to continue to support the critical work of the OpenSSF in addressing current and future threats to the broader OSS ecosystem. | ||
<p> | ||
For over a decade, I have been involved in various open source communities in professional | ||
<p> | ||
roles focused on upstream development, partner strategy and ecosystem engagement. I | ||
<p> | ||
currently lead part of Google’s Open Source Security Team, where we directly contribute to | ||
<p> | ||
critical projects and drive communication & adoption of secure software supply chain best | ||
<p> | ||
practices. I also am a founding member of the Sigstore TSC where we have built an exploding community of vendors, individuals and users focused on improving transparency of the supply chain and dramatically improving the UX for consumers and producers of OSS software. | ||
<p> | ||
As part of the OpenSSF TAC, I would continue to bring a breadth of experience and industry & academic connections to bear to help accelerate the impact of the various working groups. I am eager to support the OpenSSF's continued growth as both a forum for evangelizing best practices and as an sponsoring organization for projects that are laser-focused on helping OSS communities and users improve their security posture. | ||
</td> | ||
</tr> | ||
</table> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters