Re: [webkit-dev] Origyn BAL abstraction for WebKit: branch request

2007-11-14 Thread Jean-Charles VERDIE (Pleyo)


Le 14 nov. 07 à 07:23, Maciej Stachowiak a écrit :




I am ok with this in principle. However, in general, being on a  
branch doesn't align you with the project as closely as staying in  
sync with the trunk. In particular, there is still the risk of  
ending up diverging from the core. In particular the S60 port may  
take a long time to merge up to a more modern baseline. Still, it is  
probably better to be on a branch in webkit.org than in a completely  
separate repository, in terms of code sharing and communication.


I agree. My intention is that a branch is first step, to let us be  
closer to core source and to evangelize our vision with actual code  
within the repository, but hopefully we end up in the trunk sooner or  
later.. The sooner the better, afaic





Are there any other opinions? Besides being a meta-port, what  
specific platforms and libraries does your version of WebKit target?


If you only consider the Browser point of view, there are absolutely  
no dependency except with OWBAL APIs. These API are bound to libraries  
of course when talking about an actual port.
As far as reference  ports are concerned, targets OS are Linux 2.4 /  
2.6, uClibC (0.9.28.3 without pthread, and 0.9.29 with pthread  
activated) and libC.

WRT libs, it can be almost anything



Does anyone working on OWB already have SVN access?


Do you mean people from our repository have access to webkit SVN ?  
Nobody (except read-only of course)


Regards
Jean-Charles





Regards,
Maciej



--
Jean-Charles Verdié

A question for you: www.pleyo.com

Pleyo, CTO
mobile: +33 (0)6 282 616 05
skype: jcverdie




___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Origyn BAL abstraction for WebKit: branch request

2007-11-13 Thread Maciej Stachowiak


On Nov 12, 2007, at 3:03 AM, Jean-Charles VERDIE (Pleyo) wrote:


Dear webkit stakeholders

Back in july, Pleyo announced a new port of Webkit, not onto a  
specific platform but over an Abstraction Layer that we called OwBAL  
and which lets us address specific needs which do not perfectly fit  
with the platform approach. Actually, our goals are to be able to  
adapt WebKit not to a platform, but a set of libraries which can be  
all-but-one identical, or completely different, or whatever.  
Platform approach makes sense when porting to a comprehensive  
environment, but it does not address our needs. So that platform  
made big parts of the code redundant for us.


Today, our abstraction code is almost mature and we'd like to move  
it back to webkit.org. I believe that since our changes are quite  
intrusive in many parts of webcore, jscore and platform, a branch  
could be a good start where we could put the code so that we can  
start advocating some (if not all) of our changes to eventually end  
up being part of webkit trunk.


Can anyone tell me how to process?


I am ok with this in principle. However, in general, being on a branch  
doesn't align you with the project as closely as staying in sync with  
the trunk. In particular, there is still the risk of ending up  
diverging from the core. In particular the S60 port may take a long  
time to merge up to a more modern baseline. Still, it is probably  
better to be on a branch in webkit.org than in a completely separate  
repository, in terms of code sharing and communication.


Are there any other opinions? Besides being a meta-port, what specific  
platforms and libraries does your version of WebKit target?


Does anyone working on OWB already have SVN access?

Regards,
Maciej

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev


[webkit-dev] Origyn BAL abstraction for WebKit: branch request

2007-11-12 Thread Jean-Charles VERDIE (Pleyo)

Dear webkit stakeholders

Back in july, Pleyo announced a new port of Webkit, not onto a  
specific platform but over an Abstraction Layer that we called OwBAL  
and which lets us address specific needs which do not perfectly fit  
with the platform approach. Actually, our goals are to be able to  
adapt WebKit not to a platform, but a set of libraries which can be  
all-but-one identical, or completely different, or whatever. Platform  
approach makes sense when porting to a comprehensive environment, but  
it does not address our needs. So that platform made big parts of the  
code redundant for us.


Today, our abstraction code is almost mature and we'd like to move it  
back to webkit.org. I believe that since our changes are quite  
intrusive in many parts of webcore, jscore and platform, a branch  
could be a good start where we could put the code so that we can start  
advocating some (if not all) of our changes to eventually end up being  
part of webkit trunk.


Can anyone tell me how to process?

Best regards,
Jean-Charles

--
Jean-Charles Verdié

A question for you: www.pleyo.com

Pleyo, CTO
mobile: +33 (0)6 282 616 05
skype: jcverdie




___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev