On 04/14/2014 07:11 PM, Morgan Fainberg wrote:
> Hi everyone!
> I would like to announce my candidacy for the Technical Committee election.
> About Me
> ========
> I’m Morgan Fainberg. I am a software engineer working for a startup focused 
> on deploying OpenStack in a private cloud configuration for a number of 
> organizations. I’ve been an active member of this community since the Essex 
> release. During my involvement in OpenStack, I’ve enjoyed collaborating on 
> many OpenStack projects via code contributions, active communication and 
> collaboration. Currently I am a member of the OpenStack Identity (Keystone) 
> Core team.
> I am always in many of the OpenStack IRC channels to keep a pulse on the 
> community and be available to provide assistance with development, QA, and 
> questions on OpenStack deployments.
> Platform
> =======
> As a developer, operator, deployer, and consumer of OpenStack, I have unique 
> insight on many different facets of OpenStack. This insight and experience 
> with our strengths and weaknesses in OpenStack allows me to work with the 
> community to improve user experience for developers and deployers. This 
> improvement of user experience includes on-boarding new contributors, making 
> deployments of OpenStack easier to manage, and helping to set direction 
> across project boundaries, and to help OpenStack improve and be more complete.
> There are some key points that I would like to see the TC focus on in the 
> immediate timeline.
> Performance and Concurrency
> -----------------------------------
> A strong viable direction must be set forth on improvements and mitigating 
> regressions in performance across all OpenStack projects. This includes 
> trending, consistent testing, and even gating. There are specific projects 
> around tracking these metrics (notably Rally) which should be better 
> leveraged. The process, use of metrics, and availability of this data must be 
> formalized so that current, pre-incubated, and incubated projects will 
> perform at an acceptable standard in deployments of OpenStack.
> Inclusion of Operators in Design and Development
> ----------------------------------------------------------
> We need to be soliciting more feedback from the deployers and operators of 
> OpenStack. I view the Technical Committee as being ultimately responsible for 
> increasing the visibility of the demands of the users and operators so that 
> we (the community) can improve the usability of OpenStack. Overall, there has 
> been improvement, but in light of some of the discussions on the mailing list 
> (one example would be API major versions) we need to better include the 
> deployers, gaining a solid understanding of the impacts of a given change. 
> This concept extends further and includes improvement on the pre-incubation, 
> incubation, and integration requirements of new projects and programs. We’ve 
> seen improvement here but there is room for further discussion which should 
> absolutely involve operators to help make the best choices benefitting our 
> development community and the OpenStack deployment operators. The new 
> operator-focused sessions at the Summit are a start, but this effort will 
> require continue
d direction from the Technical Committee over the life of the development 
> Cross Project Initiatives and Communication
> ---------------------------------------------------
> There has been an overall improvement of cross-project communication and 
> facilitation of cross-project initiatives. However, I believe that the 
> Technical Committee can continue improvement on this front. This should 
> include encouragement of mid-cycle meet-ups, with potential assistance from  
> OpenStack Foundation for facilitation and funding. This cross-project 
> communication is increasing in importance as we add more OpenStack programs 
> and projects. Some of these challenges are already addressed during the 
> cross-project (and release) meetings, however, the Technical Committee has a 
> unique role to enhance and formalize these channels.
> Ease of Deployment and Usability
> ---------------------------------------
> Each release of OpenStack has improved on deployment and usability of the 
> previous release. OpenStack as a whole must continue to drive toward better 
> user experience on all fronts and the Technical Committee is ultimately 
> responsible for defining goals and means to measure improvement for each 
> release. Each incremental improvement in usability encourages wider adoption 
> of OpenStack as a valuable solution to the Virtualization and Orchestration 
> problem spaces.
> It has been a privilege to be part of the OpenStack community, and I can’t 
> wait to see where the Juno cycle will take us. I look forward to continuing 
> to serve this community as a contributor, core member of the Identity 
> Program, and an advocate of improved usability and ease of deployment.
> Cheers,
> Morgan Fainberg
> _______________________________________________
> OpenStack-dev mailing list

OpenStack-dev mailing list

Reply via email to