Hi, Didi is maintaining OTOPI and wrote with me most of the code in engine-setup back into oVirt 3.3 release. He maintained that code across the following releases along with the backup and restore tool and the rename tool. He's the most active contributor within integration team for ovirt-engine related code. I would like to propose Didi as integration maintainer for oVirt Engine.

Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> _______________________________________________ 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/JSOOG2MIPZY...

Hi, Didi is maintaining OTOPI and wrote with me most of the code in engine-setup back into oVirt 3.3 release. He maintained that code across the following releases along with the backup and restore tool and the rename tool. He's the most active contributor within integration team for ovirt-engine related code. I would like to propose Didi as integration maintainer for oVirt Engine. Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> _______________________________________________ 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/JSOOG2MIPZY...

+1 from me, too. On Tue, 5 Feb 2019 09:41:04 +0100 Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > Hi, > Didi is maintaining OTOPI and wrote with me most of the code in > engine-setup back into oVirt 3.3 release. He maintained that code across > the following releases along with the backup and restore tool and the > rename tool. He's the most active contributor within integration team for > ovirt-engine related code. > > I would like to propose Didi as integration maintainer for oVirt Engine. > > Thanks,