<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">How about creating ovirt-engine-kerbldap-migration repo under oVirt organization, pushing there content of [1] and then pushing README to [1], which will announce that project was moved under oVirt organization with link to the new repo?<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 9, 2017 at 8:20 PM, Ondra Machacek <span dir="ltr"><<a href="mailto:omachace@redhat.com" target="_blank">omachace@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hello,<br><br></div>can you please fork this[1] project to oVirt github project for better visibility?<br></div><div>Please add me(<a href="mailto:omachace@redhat.com" target="_blank">omachace@redhat.com</a>) and <a href="mailto:mperina@redhat.com" target="_blank">mperina@redhat.com</a> as maintainters.<br><br></div><div>Thanks a lot,<br></div><div>Ondra<br></div><div><br></div>[1] <a href="https://github.com/machacekondra/ovirt-engine-kerbldap-migration" target="_blank">https://github.com/<wbr>machacekondra/ovirt-engine-<wbr>kerbldap-migration</a><br></div>
</blockquote></div><br></div>