Merge pull request #1084 from matchstick/master

Automatic merge from submit-queue. .

Add Michael Rubin bio

Adding Michael Rubin bio to 2017 election.
This commit is contained in:
Kubernetes Submit Queue 2017-09-18 18:16:30 -07:00 committed by GitHub
commit 0027eefdb6
2 changed files with 37 additions and 1 deletions

View File

@ -55,7 +55,7 @@ Ihor Dvoretskyi | *TBA* | [@idvoretskyi](https://github.com/idvoretskyi)
[Justin Santa Barbara](vote_for_justinsb.md) | Independent | [@justinsb](https://github.com/justinsb)
Kris Nova | Microsoft | [@kris-nova](https://github.com/kris-nova)
[Matt Farina](mattfarina_bio.md) | Samsung SDS | [@mattfarina](https://github.com/mattfarina)
Michael Rubin | Google | [@matchstick](https://github.com/matchstick)
[Michael Rubin](michaelrubin_bio.md) | Google | [@matchstick](https://github.com/matchstick)
Michelle Noorali | Microsoft | [@michelleN](https://github.com/michelleN)
[Phillip Wittrock](pwittrock_bio.md) | Google | [@pwittrock](https://github.com/pwittrock)
Quinton Hoole | Huawei | [@quinton-hoole](https://github.com/quinton-hoole)

View File

@ -0,0 +1,36 @@
# Michael Rubin Bio
GitHub: @matchstick
## About Me
I have been a software engineer, technical manager, and leader for
~20 years. I am passionate about helping projects and people thrive.
Today I lead a number of Kubernetes teams at Google, including Storage,
Networking, Multi-cluster, Node, and more.
I love coding and technology, but even more than that I love mentoring
others and helping them to have impact and grow professionally. This is
why I choose to support teams and projects as a technical manager.
My leadership style is to bring sharp focus to technical efforts, and
to help others become successful leaders, themselves. I find that many
technology problems are not purely technical, and one of my biggest
strengths is my ability communicate, connect with people, and get to
the root of a problem. People are not machines, and they need different
skills than just pure engineering.
During my 1.5 years with Kubernetes, I have worked directly and
indirectly with several SIGs - Storage, Multi-cluster, Networking,
Scheduling, and Node. I think I have brought clarity and structure to
the efforts, helped organize priorities and roadmaps, and helped the
teams and individuals grow. I have built lasting relationships with
the people of Kubernete, and not just the code.
As a member of the Steering Committee, I would focus on:
* Cross SIG efforts and how to co-ordinate them
* Getting more things out of core, but keeping them part of Kubernetes
* Maintain the cool, open and inviting environment we have today
* Delegate and empower others by adding structure (not process)