Merge pull request #4078 from parispittman/bio

parispittman steering committee bio

events/elections/2019/README.md

@@ -23,7 +23,7 @@ whether to run or who to vote for:
   structures and policies
 * Act as a final non-technical escalation point for any Kubernetes repository
 * Request funds and other support from the CNCF (e.g. marketing, press, etc.)
-* Define and enforce requirements for community groups to be in good standing 
+* Define and enforce requirements for community groups to be in good standing
   such as having an approved charter
 
 For more context, please see the [current steering committee backlog] or a
@@ -92,7 +92,7 @@ roles you may hold.
 Kubernetes members in [voters.md] will receive a ballot via email. If you are
 not on that list and feel you have worked on Kubernetes in a way that is NOT
 reflected in GitHub contributions, you can use the [voter exemption form] to ask
-to participate in the election. 
+to participate in the election.
 
 Elections will be held using time-limited [Condorcet] ranking on [CIVS]
 using the [IRV method]. The top vote getters will be elected to the open
@@ -110,7 +110,7 @@ to the address on file at the start of the election from "Kubernetes (CIVS Poll
 Supervisor) `<civs@cs.cornell.edu>`, please whitelist if necessary. Detailed
 voting instructions will be addressed in email and the CIVS polling page. Please
 note that email ballots might be unreliable, so you are encouraged to contact
-the election officials if you do not receive a ballot by September 29. 
+the election officials if you do not receive a ballot by September 29.
 
 ### Officers
 
@@ -128,7 +128,7 @@ The newly elected body will be announced in the weekly [Kubernetes Community Mee
 on October 3, 2019.
 
 Following the meeting, the raw voting results and winners will be published on the
-[Kubernetes Blog]. 
+[Kubernetes Blog].
 
 For more information, definitions, and/or detailed election process, please refer to
 the [Steering Committee Election Charter]
@@ -144,6 +144,7 @@ the [Steering Committee Election Charter]
 |        [Klaus Ma](./klausma.md)            |        Huawei        | [@k82cn](https://github.com/k82cn)         |
 | [Vallery Lancey](./vallerylancey.md)       |         Lyft         | [@vllry](https://github.com/vllry)         |
 | [Nikhita Raghunath](./nikhitaraghunath.md) |        Loodse        | [@nikhita](https://github.com/nikhita)     |
+| [Paris Pittman](./parispittman.md)         |        Google        |[@parispittman](https://github.com/parispittman)|
 
 [Kubernetes Steering Committee]: https://github.com/kubernetes/steering
 [Steering Committee Charter]: https://github.com/kubernetes/steering/blob/master/charter.md
@@ -166,4 +167,4 @@ the [Steering Committee Election Charter]
 [Kubernetes Blog]: https://kubernetes.io/blog/
 [eligible voters]: https://github.com/kubernetes/community/blob/master/events/elections/2019/voters.md
 [voter exemption form]: https://www.surveymonkey.com/r/k8s-sc-election-2019
-[voters.md]: ./voters.md
+[voters.md]: ./voters.md

events/elections/2019/parispittman.md

@@ -0,0 +1,44 @@
+:woman_technologist: github
+[@parispittman]  
+:bird: twitter:
+[parisinbmore@]  
+:hash: slack: `paris`   
+
+## Contributions
+
+- Co-Chair, [Contributor Experience], 22 months  
+- Subproject Owner:  
+   - [contributor events] (summits, elections);
+   - community management ([operational tactics], [guidelines], and policies aligned with [governance docs] (meetings, communication, etc.) for 40+ community groups: SIGs, WGs, committees, and user groups). I call it the transparency pipelines. :smile:  
+   - [mentoring]  
+  (outreachy, #meet-our-contributors, onsite sessions at KubeCon, group mentoring, empowering SIGs to create shadow roles/teams, hands on learning, and more);
+- Member of first [Kubernetes Code of Conduct Committee]  
+- Work with Steering and/or CNCF directly on funding, process improvements, and contributor events and needs. Proposed and advocated for a contributor summit sustainability plan for a funding model that allows us to have logo free spaces among other things which aligns with our community > product or company [values].
+- I've never missed a pubic steering committee meeting to date;   
+I try to provide context to decision makers.
+
+:sparkles: tl;dr: focus on governance operations, contributor growth, advocating for contributor matters to CNCF and Steering, and trying to figure out how to glue it all together. :sparkles:  
+
+
+## What I’ll do :bowtie:
+:checkered_flag: Continue to uphold the [values],  
+:checkered_flag: Continue to clean up governance documentation, educate our large contributor base on governance topics,  
+:checkered_flag: Encourage more dialogue with the steering committee and members of the community;  
+:checkered_flag: Continue to work on project wide communications, like the [Need to Know Chairs] email, but at a steering committee level  
+:checkered_flag: Delegate decision making to the appropriate owners and/or SIGs or work to ensure there is a communicated decision making path with the committee on unresolved matters
+
+
+## Where I work
+Google
+
+[@parispittman]: https://github.com/
+[parisinbmore@]: https://twitter.com/parisinbmore
+[Contributor Experience]: https://github.com/kubernetes/community/blob/master/sig-contributor-experience/charter.md
+[contributor events]: https://github.com/kubernetes/community/tree/master/events
+[mentoring]: https://github.com/kubernetes/community/tree/master/mentoring
+[operational tactics]: https://github.com/kubernetes/community/blob/master/sig-wg-lifecycle.md
+[guidelines]: https://github.com/kubernetes/community/tree/master/communication
+[governance docs]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
+[Kubernetes Code of Conduct Committee]: https://github.com/kubernetes/community/tree/master/committee-code-of-conduct
+[values]: https://github.com/kubernetes/community/blob/master/values.md
+[Need to Know Chairs]: https://docs.google.com/document/d/1ivmV-ouim7YcTnmv21m0pP6prmj-FFZxcRBuWbT706c/edit?usp=sharing