summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAaron Schlesinger <arschles@gmail.com>2017-09-14 11:26:46 -0700
committerAaron Schlesinger <arschles@gmail.com>2017-09-14 11:26:46 -0700
commitdb0d62ea12f7311a188e39d3df4ec5efcd8238c3 (patch)
tree39603a8b5a5702bec50c4002ee88d2f195009787
parent3a7c46841eb7f134c55196957af39ab9f5510716 (diff)
trimming down the number of words
-rw-r--r--community/elections/2017/aaronschlesinger_bio.md49
1 files changed, 21 insertions, 28 deletions
diff --git a/community/elections/2017/aaronschlesinger_bio.md b/community/elections/2017/aaronschlesinger_bio.md
index 1c51cb6b..79dbd0d0 100644
--- a/community/elections/2017/aaronschlesinger_bio.md
+++ b/community/elections/2017/aaronschlesinger_bio.md
@@ -1,38 +1,32 @@
# Aaron Schlesinger
-Sr. Software Engineer, Microsoft Azure Containers Group
-
- Github: [arschles](https://github.com/arschles)
- Twitter: [@arschles](https://twitter.com/arschles)
-# About Me
+# About
-I am a former Sr. Software Engineer at Deis and part of the team that was acquired by Microsoft.
-Now, I work on Kubernetes on Azure and have the blessing of Microsoft to continue to do so.
+I'm a Sr. Software Engineer, Microsoft Azure Containers Group. I have the blessing of Microsoft
+to work on Kubernetes.
-I am a passionate engineer, teacher and leader with over 10 years software engineering and
+I'm a passionate engineer, teacher and leader with over 10 years software engineering and
architecture experience in a wide variety of fields.
-I believe that Kubernetes will truly succeed when we as a community improve the developer and
+I believe that Kubernetes will truly succeed when we improve the developer and
user experience.
-# My Experience
+# Experience
I have made contributions to [helm](https://github.com/kubernetes/helm), [helm charts](https://github.com/kubernetes/charts), [minikube](https://github.com/kubernetes/minikube), [service-catalog](https://github.com/kubernetes-incubator/service-catalog) and I am a co-lead of SIG-Service-Catalog.
-Outside of the Kubernetes world, I have spent over 10 years speaking at a diverse set of
-conferences, teaching Go on a large scale, building large distributed systems with a variety
-of technologies, sitting on standards bodies, and contributing code to other open source
-communities.
+Outside of Kubernetes, I've spent over 10 years speaking at conferences, teaching Go & Scala,
+building large systems, sitting on standards bodies, and contributing to other open source
+projects.
-# My Promises
+# Promises
-I want to share my promises to the community should I become a member of the commitee. These
-are not "campaign promises", but instead intended to reveal my motivations in the community.
-I believe in being 100% transparent on what I want to do in the community.
+Here are my promises to the community should I be elected to the committee.
-Above everything else, I want Kubernetes to be a nice place to work. And in my experience,
-a "nice place to work" means the following:
+Above all, I want Kubernetes to be a nice place to work. To me, that means the following:
- Engineers can build or improve things easily
- Engineers have clear expectations how & (generally) when they will get feedback on their work
@@ -42,20 +36,19 @@ a "nice place to work" means the following:
Holistically, most of these points are true most of the time, but Kubernetes is growing so
fast and is so diverse that all of them are not always guaranteed right now.
-_I want to work to change that._ I realize that there is no community in which all of these
-points will be true all the time, but I believe we can do better as a group.
+I realize no community can achieve everything all the time, but I believe we can do better
+together.
-Specifically, I want to improve the following immediately:
+I want to improve the following immediately:
-- Holistically improve user _and_ developer documentation
-- Provide better, clearer guidelines on how reviews should happen in all repositories
-- Make it clear how to rise as a contributor
+- Improve user _and_ developer documentation
+- Create clearer guidelines on how reviews should happen
+- Clarify how to rise as a contributor
-Beyond that, I believe that I will generally contribute best to the steering committee as a
-representative of the best interests of end users and developers at large.
+Additionally, I'll contribute best to the committee as a representative of end users
+and developers.
-I will generally keep the same promises in the steering committee as I do in
-SIG-Service-Catalog:
+I will keep the same promises in the steering committee as I do in SIG-Service-Catalog:
- **I will always seek out real user and developer opinions and viewpoints before making decisions**
- **I will always work on user & developer problems before anything else**