[openstack-dev] [Neutron] Propose Slawek Kaplonski for Neutron core

Korzeniewski, Artur artur.korzeniewski at intel.com
Wed Nov 29 20:27:28 UTC 2017


+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!

From: Miguel Angel Ajo Pelayo [mailto:majopela at redhat.com]
Sent: Wednesday, November 29, 2017 8:47 PM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at 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" <ihrachys at redhat.com<mailto:ihrachys at redhat.com>> wrote:
YES, FINALLY.

On Wed, Nov 29, 2017 at 11:29 AM, Kevin Benton <kevin at benton.pub<mailto:kevin at benton.pub>> wrote:
> +1! ... even though I haven't been around. :)
>
> On Wed, Nov 29, 2017 at 1:21 PM, Miguel Lavalle <miguel at mlavalle.com<mailto:miguel at 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-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
>>
>
>
> __________________________________________________________________________
> 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
>

__________________________________________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171129/36f6142f/attachment.html>


More information about the OpenStack-dev mailing list