[webkit-dev] Pulling together on WebKit Mobile

[Oliver Hunt]

On 11/01/2008, at 10:54 AM, Mike Emmel wrote:
> I think this approach will allow us to keep the main repository and
> tree clean and foster the churn that makes open source development fun
> and exciting.
>
> Contributing to webkit is not a fun and exciting process at the  
> moment.

There's already a git mirror of webkit trunk, and there's nothing  
stopping you from having a public facing version of your own git  
repository, but having a lax commit policy will just make life  
complicated in the long term -- say you work for many months off  
trunk, sure git will allow you to track trunk effectively, but when  
it comes to final commit time it will make reviewing the patch much  
harder as the entire patch will have to be reviewed at once...

As far as I was aware most large OSS projects had similar review  
requirements, so i'm not entirely sure how the WebKit project differs

--Oliver

>
>
> On Jan 11, 2008 10:38 AM, Alp Toker <alp at atoker.com> wrote:
>> Hey guys,
>>
>> There's a lot of mobile WebKit expertise in different  
>> organisations and
>> from various individuals, but we haven't really done much to put  
>> it all
>> in one place so far.
>>
>> Would you be interested in sharing your findings, internal  
>> documentation
>> and patches?
>>
>> Some things I'd like to see:
>>
>>   * Build fixes for various lightweight toolchains integrated into  
>> TOT
>>
>>   * Documentation of optional defines used in the WebCore loader and
>> elsewhere, like LOW_BANDWIDTH_DISPLAY and MOBILE
>>
>>   * Build instructions made public (Scratchbox, cross-compilation  
>> etc.)
>>
>>   * Compiler flags
>>
>>   * Bug workarounds for different architectures and toolchains
>>
>> I'd love to see what Naiem's team is finding and fixing in the GTK+
>> port, what tweaks the iPhone and Android engineers are using, and the
>> lightweight libc fixes from Peter, and Collabora's findings on the  
>> Nokia
>> internet tablets all in one place.
>>
>> When patches get merged, the WebKit team will help you maintain  
>> them so
>> contributing code can help reduce the burden of maintaining ports and
>> build fixes out-of-tree.
>>
>> I have some material I've built up privately in the last year on ARM
>> including benchmarks and patches that I'd like to start sharing too.
>>
>> I do think we can get more done if we work together here. I've set  
>> up a
>> wiki page -- please edit this with your findings and suggestions:
>>
>>    http://trac.webkit.org/projects/webkit/wiki/Mobile
>>
>> You can register an account on the wiki here:
>>
>>    http://trac.macosforge.org/projects/webkit/register
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo/webkit-dev
>>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo/webkit-dev