Improving the quality of OpenStack for individual users and developers.
Chris has been working with and developing various forms of distributed systems for around 25 years. When he landed in the world of OpenStack, Chris started with the Telemetry project and has since moved into improving the scheduler in Nova and helping to create the new Placement service. Chris is primarily interested in the ways groups of people use networked technology to collaborate, exploring the problem space of information sharing and reuse. He hopes to help make himself and everyone else less dumb. He is a member of the Technical Committee, a core reviewer in the API working group, and is the author of Gabbi, an HTTP testing tool, and a large suite of diverse experiments for enhancing asynchronous collaboration on the internet. In OpenStack, Chris is striving to bring about some semblance of maturity, composability and accessibility to the services while also increasing the degree of communication and transparency among the many people and organizations involved with OpenStack.
I'm involved in the following OpenStack projects: Compute Service (Nova)
I have been a technical contributor to OpenStack since early 2014, employed in roles where my primary focus was to work "upstream", first on the Telemetry (ceilometer) project and then Compute (nova). I help lead the API-SIG. I'm a member of the Technical Committee with a term that expires in April of 2018. In the last year, I have been instrumental in building a culture of increased communication and information sharing with weekly updates on the development of the Placement service and the activities of the Technical Committee. As the OpenStack community diversifies and expands, clear communication will be a huge factor in its continued success.
If elected this would be my first role as a board member of a non-profit foundation. However, In 2002 I co-founded Blue Oxen Associates, a research non-profit exploring the interaction of open source practices with the high-performance collaboration techniques espoused by Doug Engelbart. Both the research and community interaction from then remains relevant to this day.
OpenStack's relationship with its members -- corporate and individual, and with other communities is undergoing change. The Board has a critical role in encouraging continued attention from existing corporate contributors while building bridges to other communities. The recent drive to focus on the integration of multiple cloud technologies is a good step that will help ensure future flexibility and stability.
There are many things that should have the Board's focus. Choosing a top priority is impossible without reasoned review of those many things. For myself, an important priority is to provide active representation of the technical and development community to the Board and to reflect the activity of the Board back to those community members. In a time when we have renewed focus on inclusion, diversity, part-time and casual contribution, developer satisfaction, and changing corporate engagement we must be realistic about the challenges faced by individual contributors to OpenStack.
Chris has already been nominated by: