{"id":4869,"date":"2013-07-30T11:15:10","date_gmt":"2013-07-30T16:15:10","guid":{"rendered":"http:\/\/www.openstack.org\/blog\/?p=4869"},"modified":"2013-07-24T10:17:19","modified_gmt":"2013-07-24T15:17:19","slug":"open-mic-spotlight-melanie-witt","status":"publish","type":"post","link":"https:\/\/www.openstack.org\/blog\/open-mic-spotlight-melanie-witt\/","title":{"rendered":"Open Mic Spotlight: Melanie Witt"},"content":{"rendered":"<p class=\"lead\"><em><a href=\"http:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2013\/07\/Melanie-Witt.jpg\"><img loading=\"lazy\" class=\"alignright size-thumbnail wp-image-4870\" alt=\"Melanie Witt\" src=\"http:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2013\/07\/Melanie-Witt-150x150.jpg\" width=\"150\" height=\"150\" srcset=\"https:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2013\/07\/Melanie-Witt-150x150.jpg 150w, https:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2013\/07\/Melanie-Witt-300x300.jpg 300w, https:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2013\/07\/Melanie-Witt-125x125.jpg 125w, https:\/\/www.openstack.org\/blog\/wp-content\/uploads\/2013\/07\/Melanie-Witt.jpg 483w\" sizes=\"(max-width: 150px) 100vw, 150px\" \/><\/a>This post is part of the OpenStack Open Mic series to spotlight the people who have helped make OpenStack successful as we celebrate the third birthday of the project. Each day in July, a new contributor will step up to the mic and answer five questions about OpenStack, cloud, careers and what they do for fun.<\/em><\/p>\n<p><em>Melanie Witt is a software engineer working on OpenStack at Yahoo!. She\u00a0has been having fun contributing to the V3 API effort and squashing bugs\u00a0in Nova.<\/em><\/p>\n<p><strong>1. What was your first commit or contribution and why did you make it?<\/strong><\/p>\n<p>One of my first commits was a fix for a bug I uncovered while I was\u00a0working on integrating OpenStack with internal services at Yahoo!. The\u00a0bug prevented admin users from seeing a backtrace when showing a VM in\u00a0error state. This was significant because we have a lot of users, and the\u00a0more efficient it is for ops to examine errors, the better. I immediately\u00a0wanted to share the fix with other OpenStack users, and the community\u00a0makes it very easy to do.<\/p>\n<p><strong>2. What other OpenStack developers deserve a shout out for the work\u00a0<\/strong><strong>they&#8217;re doing in the community? Who are our unsung heroes? Your own?<\/strong><\/p>\n<p>I think the infrastructure team deserves a lot of recognition. The\u00a0continuous integration system is impressive. It ensures high quality of\u00a0the code base by thoroughly testing every submitted patch and merging the\u00a0code. It has been a pleasure to use.<\/p>\n<p><strong>\u00a03. What do you think are the benefits of the open, community-driven\u00a0approach to development?<\/strong><\/p>\n<p>I think gathering different perspectives is a great benefit of the open,\u00a0community-driven approach to development. Each developer comes to the\u00a0project from a different context and brings ideas from her point of view.\u00a0We have a lot to learn from each other and, by working together, we can\u00a0build something even better.<\/p>\n<p><strong>\u00a04. How do you describe OpenStack to your parents?<\/strong><\/p>\n<p>I describe it as a set of building blocks anyone can use to assemble a\u00a0computing cloud.<\/p>\n<p><strong>5. How do you think the OpenStack community will need to evolve over\u00a0the next few years in light of the fast growth and maturing user needs?<\/strong><\/p>\n<p>I think the community will focus more on performance, scalability, and\u00a0reliability as user needs mature. I see users building bigger clusters,\u00a0provisioning resources in larger volume and demanding faster performance.\u00a0The community is already moving in this direction, and I think there will\u00a0be many exciting improvements to come.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This post is part of the OpenStack Open Mic series to spotlight the people who have helped make OpenStack successful as we celebrate the third birthday of the project. Each day in July, a new contributor will step up to the mic and answer five questions about OpenStack, cloud, careers and what they do for&#8230;  <a href=\"https:\/\/www.openstack.org\/blog\/open-mic-spotlight-melanie-witt\/\" class=\"more-link\" title=\"Read Open Mic Spotlight: Melanie Witt\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":41,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[474],"tags":[465],"_links":{"self":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/4869"}],"collection":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/users\/41"}],"replies":[{"embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/comments?post=4869"}],"version-history":[{"count":2,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/4869\/revisions"}],"predecessor-version":[{"id":4872,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/posts\/4869\/revisions\/4872"}],"wp:attachment":[{"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/media?parent=4869"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/categories?post=4869"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.openstack.org\/blog\/wp-json\/wp\/v2\/tags?post=4869"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}