[webkit-efl] Moving the EFL WebKit2 public APIs to outside WebKit2 directory
Raphael Kubo da Costa
rakuco at webkit.org
Wed Jan 23 12:11:32 PST 2013
Alexis Menard <alexis at webkit.org> writes:
> On Wed, Jan 23, 2013 at 5:30 AM, Dominik Röttsches
> <dominik.rottsches at intel.com> wrote:
>> Currently, I don't think it's a good idea to do such a move. In the end, I
>> believe we are more productive when cooperating with Apple reviewers, not
>> work around them.
> Yesterday I spend sometime talking with an Apple employee and also
> spend some time thinking about it myself.
> At the end I don't think moving send the right message, in fact I'm
> pretty sure they don't want us to move out.
> So far the review time slowness is to be proven, it seems that not so
> many patches were actually pure Qt, pure EFL or pure GTK so it was
> touching the common parts with Apple. It means that in any case we
> would have to go through an Owner to get in no matter where half (or
> more) the code sit.
Alexis and Dominik, thanks for pondering the issue and expressing
everything so clearly :-)
I entirely agree with Dominik's points here: moving out of WebKit2 to
get around Apple without even talking to Apple before and making sure
everyone is aware of each other's issues and worries seems like a hushed
It's good that Alexis took the time to talk to someone at Apple (even if
privately). We now have more data to base our decisions on.
Can we agree that, if Apple is indeed willing to work with us instead of
without us, we should at least try to to coexist peacefully in WebKit2/
(while also improving our own code as we already seem to be doing)?
More information about the webkit-efl