[openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

Paul Michali pc at michali.net
Thu Jun 4 15:45:23 UTC 2015


+100 Great addition! Congratulations Assaf!

On Thu, Jun 4, 2015 at 11:41 AM Miguel Lavalle <miguel at mlavalle.com> wrote:

> Congrats! Well deserved
>
> On Thu, Jun 4, 2015 at 8:50 AM, Assaf Muller <amuller at redhat.com> wrote:
>
>> Thank you.
>>
>> We have a lot of work ahead of us :)
>>
>>
>> ----- Original Message -----
>> > It's a been a week since I proposed this, with no objections. Welcome
>> to the
>> > Neutron core reviewer team as the new QA Lieutenant Assaf!
>> >
>> > On Tue, Jun 2, 2015 at 12:35 PM, Maru Newby < marun at redhat.com > wrote:
>> >
>> >
>> > +1 from me, long overdue!
>> >
>> >
>> > > On May 28, 2015, at 9:42 AM, Kyle Mestery < mestery at mestery.com >
>> wrote:
>> > >
>> > > Folks, I'd like to propose Assaf Muller to be a member of the Neutron
>> core
>> > > reviewer team. Assaf has been a long time contributor in Neutron, and
>> he's
>> > > also recently become my testing Lieutenant. His influence and
>> knowledge in
>> > > testing will be critical to the team in Liberty and beyond. In
>> addition to
>> > > that, he's done some fabulous work for Neutron around L3 HA and DVR.
>> Assaf
>> > > has become a trusted member of our community. His review stats place
>> him
>> > > in the pack with the rest of the Neutron core reviewers.
>> > >
>> > > I'd also like to take this time to remind everyone that reviewing
>> code is a
>> > > responsibility, in Neutron the same as other projects. And core
>> reviewers
>> > > are especially beholden to this responsibility. I'd also like to
>> point out
>> > > that +1/-1 reviews are very useful, and I encourage everyone to
>> continue
>> > > reviewing code even if you are not a core reviewer.
>> > >
>> > > Existing Neutron cores, please vote +1/-1 for the addition of Assaf
>> to the
>> > > core reviewer team.
>> > >
>> > > Thanks!
>> > > Kyle
>> > >
>> > > [1] http://stackalytics.com/report/contribution/neutron-group/180
>> > >
>> __________________________________________________________________________
>> > > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150604/2b6942e0/attachment.html>


More information about the OpenStack-dev mailing list