+1 for both. -----Original Message----- From: Wenzhi Yu [mailto:wenzhi...@163.com] Sent: Tuesday, January 24, 2017 7:02 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Zun] Propose a change of the Zun core team membership
+1 from me! Kevin has made significant contribution to Zun, he deserves this! Best Regards, Wenzhi Yu(yuywz) > 在 2017年1月24日，下午5:12，Shuu Mutou <shu-mu...@rf.jp.nec.com> 写道： > > +1 for both. > > regards > Shu > > >> -----Original Message----- >> From: Pradeep Singh [mailto:ps4openst...@gmail.com] >> Sent: Tuesday, January 24, 2017 11:58 AM >> To: OpenStack Development Mailing List (not for usage questions) >> <openstack-dev@lists.openstack.org> >> Subject: Re: [openstack-dev] [Zun] Propose a change of the Zun core >> team membership >> >> +1, welcome Kevin. I appreciate your work. >> >> On Tuesday, January 24, 2017, Yanyan Hu <huyanya...@gmail.com >> <mailto:huyanya...@gmail.com> > wrote: >> >> >> ＋1 for the change. >> >> >> 2017-01-24 6:56 GMT+08:00 Hongbin Lu <hongbin...@huawei.com >> <javascript:_e(%7B%7D,'cvml','hongbin...@huawei.com');> >: >> >> >> Hi Zun cores, >> >> >> >> I proposed a change of Zun core team membership as below: >> >> >> >> + Kevin Zhao (kevin-zhao) >> >> - Haiwei Xu (xu-haiwei) >> >> >> >> Kevin has been working for Zun for a while, and made >> significant >> contribution. He submitted several non-trivial patches with high >> quality. One of his challenging task is adding support of container >> interactive mode, and it looks he is capable to handle this >> challenging task (his patches are under reviews now). I think he is a >> good addition to the core team. Haiwei is a member of the initial >> core team. Unfortunately, his activity dropped down in the past a few months. >> >> >> >> According to the OpenStack Governance process [1], we require a >> minimum of 4 +1 votes from Zun core reviewers within a 1 week voting >> window (consider this proposal as a +1 vote from me). A vote of -1 is >> a veto. If we cannot get enough votes or there is a veto vote prior >> to the end of the voting window, this proposal is rejected. >> >> >> >> [1] >> https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess >> <https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess> >> >> >> >> Best regards, >> >> Hongbin >> >> >> >> >> >> ______________________________________________________________ >> ____________ >> OpenStack Development Mailing List (not for usage >> questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> > >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack- >> dev >> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> >> >> >> >> >> >> >> -- >> >> Best regards, >> >> Yanyan > > ______________________________________________________________________ > ____ 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
