Big +1 for Slawek :) On 30/11/2017 00:49, Armando M. wrote: > On 29 November 2017 at 12:27, Korzeniewski, Artur < > artur.korzeniew...@intel.com> wrote: > >> +1 from me 😉, (even though my vote does not count) >> >> I know Slawek since Tokyo summit and I’m impressed of his knowledge and >> hands-on experience to improve Neutron quality and functionality! >> >> It is great to see him joining the core reviewers team! >> >> Congrats Sławek! >> > > Rock On > > >> >> >> *From:* Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] >> *Sent:* Wednesday, November 29, 2017 8:47 PM >> *To:* OpenStack Development Mailing List (not for usage questions) < >> openstack-dev@lists.openstack.org> >> *Subject:* Re: [openstack-dev] [Neutron] Propose Slawek Kaplonski for >> Neutron core >> >> >> >> "+1" I know, I'm not active, but I care about neutron, and slaweq is a >> great contributor. >> >> >> >> On Nov 29, 2017 8:37 PM, "Ihar Hrachyshka" <ihrac...@redhat.com> wrote: >> >> YES, FINALLY. >> >> On Wed, Nov 29, 2017 at 11:29 AM, Kevin Benton <ke...@benton.pub> wrote: >>> +1! ... even though I haven't been around. :) >>> >>> On Wed, Nov 29, 2017 at 1:21 PM, Miguel Lavalle <mig...@mlavalle.com> >> wrote: >>>> >>>> Hi Neutron Team, >>>> >>>> I want to nominate Slawek Kaplonski (irc: slaweq) to Neutron core. >> Slawek >>>> has been an active contributor to the project since the Mitaka cycle. >> He has >>>> been instrumental in the development of the QoS capabilities in Neutron, >>>> becoming the lead of the sub-team focused on that set of features. More >>>> recently, he has collaborated in the implementation of OVO and is an >> active >>>> participant in the CI sub-team. His number of code reviews during the >> Queens >>>> cycle is on par with the leading core members of the team: >>>> http://stackalytics.com/?module=neutron >>>> >>>> In my opinion, his efforts are highly valuable to the team and we will >> be >>>> very lucky to have him as a fully voting core. >>>> >>>> I will keep this nomination open for a week as customary, >>>> >>>> Thank you, >>>> >>>> Miguel >>>> >>>> ____________________________________________________________ >> ______________ >>>> OpenStack Development Mailing List (not for usage questions) >>>> Unsubscribe: openstack-dev-requ...@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-requ...@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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev