Merge pull request #1040 from lxpollitt/lxpollitt-bio-1

Automatic merge from submit-queue

Alex Pollitt bio for steering committee voter guide
This commit is contained in:
Kubernetes Submit Queue 2017-09-13 10:37:03 -07:00 committed by GitHub
commit 4a1e2b8545
2 changed files with 28 additions and 1 deletions

View File

@ -43,7 +43,7 @@ Name | Organization/Company | GitHub
Aaron Crickenberger | Samsung SDS | [@spiffxp](https://github.com/spiffxp)
Aaron Schlesinger | Microsoft | [@arschles](https://github.com/arschles)
Adnan Abdulhussein | Bitnami | [@prydonius](https://github.com/prydonius)
Alex Pollitt | Tigera | [@lxpollitt](https://github.com/lxpollitt)
[Alex Pollitt](alexpollitt_bio.md) | Tigera | [@lxpollitt](https://github.com/lxpollitt)
[Caleb Miles](calebamiles_bio.md) | CoreOS | [@calebamiles](https://github.com/calebamiles)
Derek Carr | Red Hat | [@derekwaynecarr](https://github.com/derekwaynecarr)
Doug Davis | IBM | [@duglin](https://github.com/duglin)

View File

@ -0,0 +1,27 @@
# Alex Pollitt
I am excited to have been nominated for the steering committee. I recognize that doing
the role justice will be a demanding and time consuming commitment, but I would like
to do my part to help maintain and foster the growth of this amazing community of
contributors and users.
For those of you who dont know me, I am one of the founders of Tigera, the company behind
Calico, and active contributors to flannel, CNI, Kubernetes, and Istio. Ive been working
with the Kubernetes community since 2014 and have great respect for everyone Ive had the
chance to get to know along the way.
Since the early days of the project, when friends used to ask, “which container orchestrator
would you bet on?”, my answer was always Kubernetes not because of the great design
principles, but because of how the founding team and those already contributing welcomed
others to take part and collaborate with an equal voice to move the project forward. For me,
“Kubernetes” means the people and how they work together, as much as technology.
One example I experienced was the k8s-sig-net efforts to agree a network policy API. In
other communities, this might have descended into vendors trying to get one up on each
other. Instead there was true collaboration, focusing on technical merit and meeting the needs
of future users. It was awesome to play a part in that process and even though it was just one
small corner of Kubernetes its a great illustration of why I love working in this community.
If elected, I promise to do my utmost to foster and facilitate this kind of diverse, vendor
neutral, merit based collaboration, empower and support contributors to shape the project,
and maintain the spirit of this awesome community as it grows.