[openstack-dev] [Mistral] Propose Winson Chan m4dcoder for core team

Anastasia Kuznetsova akuznetsova at mirantis.com
Tue Apr 7 13:28:36 UTC 2015


Hello all,

As a QA Engineer of Mistral, I also appreciate Winson's contribution to the
project, his ideas and I will be glad to see him as a core engineer of
Mistral project.

On Tue, Apr 7, 2015 at 12:56 PM, Lingxian Kong <anlin.kong at gmail.com> wrote:

> Although I have jumpped into Mistral just for a short time, but really
> appreciate Winson's vision about my patches, and his work is of great
> value to Mistral.
>
> I'm not in the core team of Mistral, but really hope to see Winson as
> a core member to bring more to Mistral.
>
> On Tue, Apr 7, 2015 at 5:08 PM, Nikolay Makhotkin
> <nmakhotkin at mirantis.com> wrote:
> > It would be good to see Winson as the core contributor in Mistral.
> >
> > +1 for Winson!
> >
> >
> >
> > On Tue, Apr 7, 2015 at 11:53 AM, Renat Akhmerov <rakhmerov at mirantis.com>
> > wrote:
> >>
> >> +1 with my both hands. Winson has been working on Mistral for about a
> >> year, was actively participating in the very first workflow engine
> version
> >> (what we called PoC) and keeps bringing his experience and excellent
> >> engineering skills to the project.
> >>
> >> Thanks Winson for your passionate work!
> >>
> >> Renat Akhmerov
> >> @ Mirantis Inc.
> >>
> >>
> >>
> >> > On 07 Apr 2015, at 03:04, Dmitri Zimine <dzimine at stackstorm.com>
> wrote:
> >> >
> >> > Hi folks,
> >> >
> >> > I’d like to propose Winson Chan (m4dcoder) to become Mistral core team
> >> > member.
> >> >
> >> > Winson brings unique mix of field experience implementing Mistral
> >> > workflows in user environments, and solid development skills.
> >> >
> >> > He has been contributing to Mistral since Mar 2014. Winson did a 23
> >> > commits - a number of them are non-trivial, like moving RPC to
> >> > oslo-messaging, or introducing environments, or making full
> validation. He
> >> > has submitted 14 blueprints and detailed design proposals,
> contributing to
> >> > design and directions. He found, reported, and fixed bugs. He is
> becoming
> >> > more active on the review board (would encourage to do more).
> >> >
> >> > I am +1 for m4dcoder as a core team member.
> >> >
> >> > DZ.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> __________________________________________________________________________
> >> > 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
> >
> >
> >
> >
> > --
> > Best Regards,
> > Nikolay
> >
> >
> __________________________________________________________________________
> > 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
> >
>
>
>
> --
> Regards!
> -----------------------------------
> Lingxian Kong
>
> __________________________________________________________________________
> 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
>



-- 
Best regards,
Anastasia Kuznetsova
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150407/0ef1aca1/attachment.html>


More information about the OpenStack-dev mailing list