Currently the WebKit/Owners file states the following All patches to WebKit2 must be reviewed and/or authored by one of the following: The policy should be more explicit on what parts of WebKit require an Owner to review so other WebKit reviewers know which patches they are and are not allowed to review within this part of the code.
My understanding is that a reviewer should for sure be involved in anything involving the shared C API and IPC code but I don't think there's been an official stance on this.
(In reply to Don Olmstead from comment #1) > My understanding is that a reviewer should for sure be involved in anything > involving the shared C API and IPC code but I don't think there's been an > official stance on this. My understanding is that any cross-platform WebKit2 code needs WK2 Owner approval. That would include cross-platform IPC and shared C API. I personally think that an IPC that is specific to your port does not need owner approval, similarly to any code that is specific to your port.
The policy applies to any code change in the Source/WebKit directory. If it is code that is only compiled for your port, then you're probably ok, but if you're exposing something in your API that isn't exposed in the owners' APIs then you should definitely consult an owner because we may intend to do substantial changes that may break your newly-exposed API.
[webkit-dev] OWNERS policy https://lists.webkit.org/pipermail/webkit-dev/2018-February/029884.html