Open Stack

I’m not a core, so treat this as +0 but I think Jakub will be good addition to core team.

So +1

> On Jul 22, 2016, at 3:20 AM, Martin Hickey <martin.hickey at ie.ibm.com> wrote:
> 
> +1
> 
> <graycol.gif>Oleg Bondarev ---22/07/2016 09:13:16---+1 On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley <dougwig at parksidesoftware.com>
> 
> From: Oleg Bondarev <obondarev at mirantis.com>
> To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
> Date: 22/07/2016 09:13
> Subject: Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testing core
> 
> 
> 
> 
> +1
> 
> On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley <dougwig at parksidesoftware.com <mailto:dougwig at parksidesoftware.com>> wrote:
> +1
> On Jul 21, 2016, at 5:13 PM, Kevin Benton <kevin at benton.pub <mailto:kevin at benton.pub>> wrote:
> 
> +1
> 
> On Thu, Jul 21, 2016 at 2:41 PM, Carl Baldwin <carl at ecbaldwin.net <mailto:carl at ecbaldwin.net>> wrote:
> +1 from me
> 
> On Thu, Jul 21, 2016 at 1:35 PM, Assaf Muller <assaf at redhat.com <mailto:assaf at redhat.com>> wrote:
> 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 <http://stackalytics.com/report/contribution/neutron/90>
> [2] http://docs.openstack.org/developer/neutron/policies/neutron-teams.html <http://docs.openstack.org/developer/neutron/policies/neutron-teams.html>
> [3] http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron <http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron>
> [4] https://assafmuller.com/2015/05/17/testing-lightning-talk/ <https://assafmuller.com/2015/05/17/testing-lightning-talk/>
> [5] https://etherpad.openstack.org/p/neutron-tempest-defork <https://etherpad.openstack.org/p/neutron-tempest-defork>
> [6] https://www.youtube.com/watch?v=a0qlsH1hoKs&feature=youtu.be&t=24m22s <https://www.youtube.com/watch?v=a0qlsH1hoKs&feature=youtu.be&t=24m22s>
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org <mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160722/54244f5a/attachment.html>