<div dir="ltr"><div>Hi,</div><div><br></div>If there is no other active maintainer for EFL port, unfortunately I have to agree to drop EFL port in mainline<div>because EFL port should not be an obstacle. I will maintain WebKitEFL like the QT port in </div><div><a href="https://github.com/Gyuyoung/ewebkit">https://github.com/Gyuyoung/ewebkit</a> and <a href="http://www.ewebkit.org">http://www.ewebkit.org</a>.</div><div><div><br></div><div>Gyuyoung.</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 15, 2017 at 6:25 AM, Alex Christensen <span dir="ltr"><<a href="mailto:achristensen@apple.com" target="_blank">achristensen@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><span class=""><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Konstantin Tokarev maintains a Qt port at <a href="https://github.com/annulen/webkit" target="_blank">https://github.com/annulen/<wbr>webkit</a> - sounds like you could do something like that.</div></div></blockquote></span>We have accepted the upstreaming of many patches from this repository into WebKit. That reduces Konstantin’s maintenance burden and makes WebKit better organized without holding back our development.<br></div><br></div><br>______________________________<wbr>_________________<br>
webkit-dev mailing list<br>
<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a><br>
<a href="https://lists.webkit.org/mailman/listinfo/webkit-dev" rel="noreferrer" target="_blank">https://lists.webkit.org/<wbr>mailman/listinfo/webkit-dev</a><br>
<br></blockquote></div><br></div>