2:35 p.m.
+1
Thanks,
Edy.
> On 4 Jun 2018, at 13:47, Dan Kenigsberg <danken(a)redhat.com> wrote:
>
> Approved.
>
> On Mon, Jun 4, 2018 at 12:02 PM, Piotr Kliczewski
> <piotr.kliczewski(a)gmail.com> wrote:
>> +1
>>
>>> On Thu, May 31, 2018 at 8:39 AM, Arik Hadas <ahadas(a)redhat.com> wrote:
>>>
>>>
>>>> On Thu, May 31, 2018 at 1:46 AM, Nir Soffer <nsoffer(a)redhat.com>
wrote:
>>>>
>>>> On Wed, May 30, 2018 at 11:23 AM Francesco Romani
<fromani(a)redhat.com>
>>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> Milan Zamazal has been working on the oVirt project for more than
2.5
>>>>> years.
>>>>> Let me highlight some of his many contributions to the project:
>>>>>
>>>>> - Since January this year - 2018, he's been a maintainer for the
stable
>>>>> branches.
>>>>> - He developed important features like memory hotunplug, which
required
>>>>> tight cooperation
>>>>> and communication with the other layers of the stack (libvirt,
qemu).
>>>>> - He is a mentor in the Outreachy program, which lead to creation of
the
>>>>> oVirt Log Analyzer: https://github.com/mz-pdm/ovirt-log-analyzer
>>>>> - He contributed more than 290 patches to the Vdsm project in master
>>>>> branch alone, excluding backports and contributions to Engine
>>>>> - He contributed and is contributing testcases and fixes to the
oVirt
>>>>> System Test suite, a tool which was already pivotal in ensuring the
>>>>> quality of the oVirt project.
>>>>>
>>>>> As reviewer, Milan is responsive and his comments are always
>>>>> comprehensive and well focused,
>>>>> with strong attitude towards getting things done and done right.
>>>>>
>>>>> Milan also demonstrated his ability to adapt to the needs of the
project:
>>>>> - he demonstrated careful and thoughtful patch management while
>>>>> maintaining the stable branches
>>>>> - he also demonstrated he's not shy to tackle large and needed
changes
>>>>> during the 4.1 and 4.2 cycles,
>>>>> when we deeply reorganized the XML processing in the virt code.
>>>>>
>>>>> For those reasons, and many more, I think he will be a good addition
to
>>>>> the maintainers team, and I propose him as virt co-maintainer.
>>>>>
>>>>> Please share your thoughts
>>>>
>>>>
>>>> +1
>>>
>>>
>>> FWIW, +1
>>>
>>>>
>>>>
>>>> Nir
>>>>
>>>>
>>>> _______________________________________________
>>>> Devel mailing list -- devel(a)ovirt.org
>>>> To unsubscribe send an email to devel-leave(a)ovirt.org
>>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>>> oVirt Code of Conduct:
>>>> https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/QELJ7YNZVW6...
>>>>
>>>
>>>
>>> _______________________________________________
>>> Devel mailing list -- devel(a)ovirt.org
>>> To unsubscribe send an email to devel-leave(a)ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YIMB6QHQ37D...
>>>
>> _______________________________________________
>> Devel mailing list -- devel(a)ovirt.org
>> To unsubscribe send an email to devel-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YBK7IHQELSE...