+1
On 22/02/16 03:23, Jeffrey Zhang wrote:
+1 Nick work!
On Mon, Feb 22, 2016 at 10:27 AM, Ryan Hallisey <rhall...@redhat.com
<mailto:rhall...@redhat.com>> wrote:
+1. Nice work Angus!
-Ryan
> On Feb 19, 2016, at 11:51 PM, Michał Jastrzębski
<inc...@gmail.com <mailto:inc...@gmail.com>> wrote:
>
> +1 on condition that he will appear in kolla itself, after
> all...you'll be a kolla core as well right?;)
>
>> On 19 February 2016 at 21:44, Sam Yaple <sam...@yaple.net
<mailto:sam...@yaple.net>> wrote:
>> +1 of course. I mean, its Angus. Who can say no to Angus?
>>
>> Sam Yaple
>>
>> On Fri, Feb 19, 2016 at 10:57 PM, Michal Rostecki
<mroste...@mirantis.com <mailto:mroste...@mirantis.com>>
>> wrote:
>>>
>>>> On 02/19/2016 07:04 PM, Steven Dake (stdake) wrote:
>>>>
>>>> Angus is already in kolla-mesos-core but doesn't have broad
ability to
>>>> approve changes for all of kolla-core. We agreed by majority
vote in
>>>> Tokyo that folks in kolla-mesos-core that integrated well with the
>>>> project would be moved from kolla-mesos-core to kolla-core. Once
>>>> kolla-mesos-core is empty, we will deprecate that group.
>>>>
>>>> Angus has clearly shown his commitment to Kolla:
>>>> He is #9 in reviews for Mitaka and #3 in commits(!) as well as
shows a
>>>> solid PDE of 64 (meaning 64 days of interaction with either
reviews,
>>>> commits, or mailing list participation.
>>>>
>>>> Count my vote as a +1. If your on the fence, feel free to
abstain. A
>>>> vote of –1 is a VETO vote, which terminates the voting
process. If
>>>> there is unanimous approval prior to February 26, or a veto
vote, the
>>>> voting will be closed and appropriate changes made.
>>>>
>>>> Remember now we agreed it takes a majority vote to approve a core
>>>> reviewer, which means Angus needs a +1 support from at least 6
core
>>>> reviewers with no veto votes.
>>>>
>>>> Regards,
>>>> -steve
>>>
>>> +1
>>> Good job, Angus!
>>>
>>>
__________________________________________________________________________
>>> 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
>>
>>
>>
>>
__________________________________________________________________________
>> 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
>
>
__________________________________________________________________________
> 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
__________________________________________________________________________
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
--
Jeffrey Zhang
Blog: http://xcodest.me <http://xcodest.me/>
__________________________________________________________________________
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
