[webkit-dev] Changes to the WebKit2 development process

Thiago Marcos P. Santos tmpsantos at gmail.com
Wed Jan 9 02:04:15 PST 2013

On Wed, Jan 9, 2013 at 11:32 AM, Simon Hausmann
<simon.hausmann at digia.com> wrote:
> On Tuesday, January 08, 2013 02:57:53 PM Sam Weinig wrote:
>> Hello webkit-dev,
>> We are making some changes to the development process for WebKit2. These
>> changes were announced to reviewers in advance, and I'd like to share them
>> with you now.
>> WebKit2 has a core set of functionality that is valuable to all ports, and
>> then aspects that are only of limited/specialized interest. It is becoming
>> increasingly difficult to improve and advance the core functionality while
>> maintaining the more peripheral aspects. In addition, changes to the core
>> often require significant expertise to evaluate, for instance to ensure
>> that the security and responsiveness goals of WebKit2 are met.
>> The changes are:
>> 1) WebKit2 now has owners. Only owners should review WebKit2 patches. While
>> we do not want to apply this concept across the whole WebKit project at
>> this time, for WebKit2 it is appropriate. The list of owners is documented
>> in the Owners file at the WebKit2 top level directory, and in
>> committers.py.
> I think the fact that the regular WebKit review process stops at the boundary
> of WebKit2 should be documented in the WebKit Committers and Reviewer Policy.

Agree. And please clarify on the policy if we are talking about
everything inside the WebKit2/ directory or if we have exceptions. It
is not clear to me if port specific code is covered by this rule and
should by reviewed by the owners. And what about code shared by Qt,
GTK and EFL (i.e. Platform/CoreIPC/unix/) but not used by Mac?

- Thiago

More information about the webkit-dev mailing list