github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-08-30 14:25:43 +00:00
Code Issues Projects Releases Wiki Activity

election: 2023-10: Add Jeremi Piotrowski candidacy

Browse Source 
Throwing my hat in the ring.

Fixes: #357
Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
This commit is contained in:
Jeremi Piotrowski 2023-10-11 11:55:21 +02:00
parent 4639f5ad80
commit 9336bd30ad
1 changed files with 38 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
elections/arch-committee-2023-10/JeremiPiotrowski.txt Normal file
View File

@ -0,0 +1,38 @@
Name: Jeremi Piotrowski
Email: jpiotrowski@microsoft.com
Background:
I'm a software engineer at Microsoft, where I work within Azure. My primary
focus is contributing to open source projects within the Cloud Native space,
but I do not draw the line there and try to improve any and every part of the
stack involved in running containers.
For more than a year now I have been active in both the Kata Containers and
Confidential Containers communities. I have been working in numerous areas most
recently CI stability, and reviewing contributions (especially Cloud-Hypervisor
related) to ensure the project can incorporate them in a timely manner. Other
areas I've helped with are CoCo releases, CoCo development related to
attestation (TDX and SNP) and bugfixes in Kata (cgroups and others). You may
also have seen me answering questions on slack and helping others understand
the Kata design or debugging issues.
Microsoft relies on Kata Containers in some of our service offerings, with more
to come. We sponsor both the Kata as well CoCo CI infrastructures. We are also
active in adjacent projects like Cloud Hypervisor. Our goal within the Kata
project is simple: contribute to the security and reliability of the project
and help make it suitable for an even wider range of use cases. Part of this is
taking our learnings from years of running hardware isolated containers and
confidential computing workloads in production and contributing them to the
project, in a way that benefits all users.
Joining the Kata Architecure Committee will give me a chance to better serve
the community. Kata is a very dynamic and friendly project, and I'd like to
contribute directly to that. I care about making the project more robust as the
codebase grows, improving our test and release processes and making it is
easier for new contributors to join the project. I also want to work within the
AC to see if we can reconcile some of the extensions that the community has
built up around Kata.
Jeremi