Jump to: navigation, search

Cinder/PTLCandidates/Fall2012/JohnGriffith

< Cinder
Revision as of 15:49, 31 August 2012 by John (talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

John Griffith

irc: jgriffith

Personal Bio

I'm a software engineer with a diverse engineering background in the storage industry for the last 15 years. My background includes everything from hardware design to linux kernel drivers, to test automation design as well as management API design and implementation. I'm passionate about Open Source software and the importance of giving back.

OpenStack Bio

Qualifications:

I've been an active contributor to Nova since November of 2011, starting out as many by adding a driver, but then began helping out anywhere and everywhere I could. IRC questions/conversations, assigning bugs to myself and working on them etc.

Contribution over the last six months:

During the last summit I lead conversations around the idea of Cinder and organized the effort to kick off the project. Since then I've been acting as interim PTL for the project and have successfully driven the effort to promote Cinder to core status as an OpenStack project.

While it's been a learning experience I have been fulfilling the responsibilities or PTL, this includes dedicated time, contributions in the form of code, approvals, bug triage and participation in the project team meetings. I have dedicated all of my time and energy to the Cinder project.

Most critical aspects for Cinder in the next 6 months:

The next six months are going to be detrimental to Cinder. The most important thing is going to be showing a smooth transition from Nova-Volume to Cinder is possible. There's a lot of concern regarding this subject and it's something that I keep in mind with any change/fix or addition to the code.

Aside from the initial release, the critical aspects for Grizzly are going to be gain momentum, focus on quality and provide new features. Quality is my number one priority, and I think there is a lot of potential to harden the core code in the project and greatly improve the user experience as well as capabilities.