some notes about Safari team plans for WebCore and JavaScriptCore

[Darin Adler]

On Tuesday, July 22, 2003, at 02:55 PM, Dirk Mueller wrote:

>> - Although we don't want to rule it out permanently, we don't plan to 
>> share a single source tree with the KDE original of KHTML any time in 
>> the foreseeable future.
>
> Can you elaborate on the reasons behind this decision?

Here's one reason we won't do this any time soon:

- Our team needs to be able to control what goes into our tree; there 
are at least some changes that happen in the KDE version that we don't 
want. I'm certain there are also changes we have made that you don't 
want, given things that have been said on this mailing list.

Here are a few other considerations:

- Our schedules are different; a current example is that we have been 
doing lots of active development, and shipped 1.0 recently. KDE head is 
not considered stable at this point, yet WebCore has many differences 
from the KDE 3.1 branch.
- Our team uses a process where we require review of each change as it 
is landed, which is different from the process used in KDE.
- A lot of work will be required to make this happen; our first 
priority is the bug fixes and features for our upcoming releases.

There are probably others. I haven't tried to make an exhaustive list.

There may be some way of resolving many of these issues in the long 
run, depending on how comfortable you are doing KDE development with 
the policies we use on the Safari team.

     -- Darin