[openstack-dev] TC candidacy

Tristan Cacqueray tristan.cacqueray at enovance.com
Wed Apr 16 07:24:08 UTC 2014


confirmed

On 04/16/2014 04:53 AM, Joe Gordon wrote:
> Hi All,
> 
> I'd like to announce my candidacy for the Technical Committee election.
> 
> About Me
> --------------
> 
> I work full time on OpenStack on behalf of HP. And am part of nova-core,
> nova-specs-core, hacking-core and elastic-recheck-core. Some of my more
> visible accomplishments outside my involvement in nova are:
> 
> - Creating hacking [0][1] to more efficiently use reviewers time by
> automating the tedious job of checking style.
> 
> - Starting elastic-recheck [2][3] to help us better track and triage race
> conditions.
> 
> - Helping Unwedge the gate right before the release of Havana [4].
> 
> - Writing several gating jobs: large-ops, neutron-large-ops and nova’s
> partial-ncpu. partial-ncpu is nova’s gating test to make sure we support
>  doing a rolling upgrade of compute nodes (so a Havana nova-compute should
> work with an Icehouse cloud).
> 
> 
> 
> My Platform
> 
> ------------------
> 
> 
> I think the Icehouse TC has done a wonderful job and has an impressive list
> of accomplishments [4], and I would like to see the TC do more of the same
> at an accelerated pace. Given the scale of OpenStack today I don’t think
> sitting on the TC should be a two hour a week job. Note: I am not pushing
> for more frequent meetings, but rather more ‘homework.’ Two hours a week
> was fine when OpenStack had 3 integrated projects, but not so much now that
> we are at 11 integrated projects. Besides just doing more of the same, here
> are a few specific areas where I think the TC can be improved:
> 
> - Make the mid-cycle incubation status reviews [6] more thorough, and
> extend them to projects that are planning on filing for incubation. We
> don’t want a repeat of what happened this past cycle where a project passed
> its mid-cycle incubation status review [6], only to hit significant issues
> in its graduation request [7]. - TC members who are not too familiar with
> the project in question should do the gap analysis instead of a member of
> that project. A fresh pair of eyes is always a good thing, and this will
> help increase cross project feedback.
> 
> 
> 
> Thank you for your consideration.
> 
> 
> Best,
> 
> Joe
> 
> 
> 
> [0] http://git.openstack.org/cgit/openstack-dev/hacking
> 
> [1] http://docs.openstack.org/developer/hacking/
> 
> [2] http://git.openstack.org/cgit/openstack-infra/elastic-recheck/
> 
> [3] http://status.openstack.org/elastic-recheck/
> 
> [4]
> http://lists.openstack.org/pipermail/openstack-dev/2013-November/020280.html
> [5]
> http://lists.openstack.org/pipermail/openstack-dev/2014-April/032576.html[6]
> http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-01-21-20.03.html[7]
> http://lists.openstack.org/pipermail/openstack-dev/2014-March/030638.html
> 
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140416/7926952f/attachment.pgp>


More information about the OpenStack-dev mailing list