Re: [webkit-dev] OWNERS policy

2018-02-21 Thread Michael Catanzaro
On Wed, Feb 21, 2018 at 2:52 PM, don.olmst...@sony.com wrote: One thing we're unclear on is the OWNERS policy. The list itself is pretty small and has no guidance on who might be the right person(s) to assign a bug to when touching shared code. It feels like we're just guessing on reviewers

Re: [webkit-dev] OWNERS policy

2018-02-21 Thread Ryosuke Niwa
If there was any confusion, WebKit2 Owner's policy is still active and in effect. In the case you aren't sure of the right reviewer, you can send a bulk email to all of us. I get cc'ed on every WebKit bug with Mac EWS/CQ failure, and as such, I ignore all WebKit bugs I'm cc'ed unless the bug

Re: [webkit-dev] OWNERS policy

2018-02-21 Thread youenn fablet
Hi Don, I am not sure there is a well defined policy. If we want to continue with owners, it would indeed be good to make it clearer and more functional. Here is my current understanding. The multi-process architecture is now well in place so things like updating IPC encoders/decoders might no

[webkit-dev] OWNERS policy

2018-02-21 Thread Don.Olmstead
Hi WebKittens, As you know we're working on getting WinCairo running on modern WebKit. We're working through a backlog of patches we have to upstream and are sometimes running into issues where we can't find reviewers for our code. Here are some bugs with attachments that have been hanging out

Re: [webkit-dev] A couple more build flags to review

2018-02-21 Thread Michael Catanzaro
On Tue, Feb 20, 2018 at 1:09 PM, Michael Catanzaro wrote: There's also ENABLE_LINK_PREFETCH. Looks like this has a cross-platform implementation, so I'm a bit surprised it is disabled everywhere. What should be do with this? Relevant bug: