As Neutron's so called testing lieutenant I would like to propose Jakub Libosvar to be a core in the testing area. Jakub has demonstrated his inherent interest in the testing area over the last few years, his reviews are consistently insightful and his numbers [1] are in line with others and I know will improve if given the responsibilities of a core reviewer. Jakub is deeply involved with the project's testing infrastructures and CI systems. As a reminder the expectation from cores is found here [2], and specifically for cores interesting in helping out shaping Neutron's testing story: * Guide community members to craft a testing strategy for features [3] * Ensure Neutron's testing infrastructures are sufficiently sophisticated to achieve the above. * Provide leadership when determining testing Do's & Don'ts [4]. What makes for an effective test? * Ensure the gate stays consistently green And more tactically we're looking at finishing the Tempest/Neutron tests dedup [5] and to provide visual graphing for historical control and data plane performance results similar to [6]. [1] http://stackalytics.com/report/contribution/neutron/90 [2] http://docs.openstack.org/developer/neutron/policies/neutron-teams.html [3] http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron [4] https://assafmuller.com/2015/05/17/testing-lightning-talk/ [5] https://etherpad.openstack.org/p/neutron-tempest-defork [6] https://www.youtube.com/watch?v=a0qlsH1hoKs&feature=youtu.be&t=24m22s