[webkit-dev] OWNERS policy

[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 longer require a dedicated owner scrutiny.
Exposing the right WK2 APIs is more sensitive on the other hand.

   Y

Le mer. 21 févr. 2018 à 12:52, <Don.Olmstead at sony.com> a écrit :

> 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 for over 5
> days.
>
>
>
> https://bugs.webkit.org/show_bug.cgi?id=182870
>
> https://bugs.webkit.org/show_bug.cgi?id=182869
>
> https://bugs.webkit.org/show_bug.cgi?id=182751
>
>
>
> 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 which doesn't seem like it helps anything move along.
>
>
>
> There also seem to be commits that were reviewed by non-owners that are
> touching common code. We're not sure if unfamiliarity with Windows might
> prevent some owners from looking over a patch as we move further along in
> our implementation.
>
>
>
> Basically we'd like to get some clarification here so we can keep landing
> patches for modern WebKit on Windows.
>
>
>
> Thanks!
>
> Sony WebKit Team
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20180221/cb81c665/attachment.html>