[openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

Gary Kotton gkotton at vmware.com
Sun Jul 24 08:07:33 UTC 2016


+1

On 7/22/16, 9:49 PM, "Brandon Logan" <brandon.logan at RACKSPACE.COM> wrote:

    +1
    
    
    
    On Fri, 2016-07-22 at 09:19 -0500, Darek Śmigiel wrote:
    
    > 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> wrote:
    
    > >         +1
    
    > >                         On Jul 21, 2016, at 5:13 PM, Kevin Benton
    
    > >                         <kevin at benton.pub> wrote:
    
    > >                         
    
    > >                         +1
    
    > >                         
    
    > >                         On Thu, Jul 21, 2016 at 2:41 PM, Carl
    
    > >                         Baldwin <carl at ecbaldwin.net> wrote:
    
    > >                         +1 from me
    
    > >                         
    
    > >                         On Thu, Jul 21, 2016 at 1:35 PM, Assaf
    
    > >                         Muller <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]
    
    > >                                 https://urldefense.proofpoint.com/v2/url?u=http-3A__stackalytics.com_report_contribution_neutron_90&d=CwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=vzH--HSno3OzeLPi1x2l2Z5AYyW6MSlzhGr1RFbm9XI&s=RybheckohLobHhlMQjVZLb4FcK1EKG0VtOMCSfyJefA&e= 
    
    > >                                 [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://urldefense.proofpoint.com/v2/url?u=https-3A__assafmuller.com_2015_05_17_testing-2Dlightning-2Dtalk_&d=CwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=vzH--HSno3OzeLPi1x2l2Z5AYyW6MSlzhGr1RFbm9XI&s=sYj2F7IQ3_RWIlKVSOz0kcIxWm13ykT4I8_6WVVxiSI&e= 
    
    > >                                 [5]
    
    > >                                 https://etherpad.openstack.org/p/neutron-tempest-defork
    
    > >                                 [6]
    
    > >                                 https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_watch-3Fv-3Da0qlsH1hoKs-26feature-3Dyoutu.be-26t-3D24m22s&d=CwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=vzH--HSno3OzeLPi1x2l2Z5AYyW6MSlzhGr1RFbm9XI&s=NeW_Anf0wCbXV1EmX3Xa5S16b0_J_VrWm1tljVzRZbk&e= 
    
    > >                                 
    
    > >                                 __________________________________________________________________________
    
    > >                                 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
    
    > >                         
    
    > >                         
    
    > >                         __________________________________________________________________________
    
    > >                         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
    
    > >                         
    
    > >                         
    
    > >                         __________________________________________________________________________
    
    > >                         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
    
    > >         
    
    > >         
    
    > >         __________________________________________________________________________
    
    > >         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
    
    > > __________________________________________________________________________
    
    > > 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
    
    > > 
    
    > > 
    
    > > 
    
    > > 
    
    > > __________________________________________________________________________
    
    > > 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
    
    > > 
    
    > 
    
    > 
    
    > __________________________________________________________________________
    
    > 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
    
    
    
    __________________________________________________________________________
    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
    



More information about the OpenStack-dev mailing list