Helping with 16401.master

= join webkit project = ok – the first things you will need to do is join webkit-dev, and also register a bugs.webkit.org account. you’ll be working with these people: <ul> <li>Gustavo Noronha (kov, review+)</li> <li>Alp Toker (alp, review+)</li> <li>Holger Freyther (zecke, review+)</li> <li>Jan Alonzo (janm, review+)</li> </ul> they’ll be advising you of the process by which the patches can be what they call “landed”. they will take us through step by step in the review and quality assurance procedures which have been built up over several years. they will also be very patient with you, and will accomodate your skills and level of experience, and will guide you patiently and expertly to see this work through. = get current work = the second thing that you’ll need to do is to obtain a copy of the current work: http://github.com/lkcl/webkit/tree/16401.master the important things to pay attention to are: <ul> <li>the file 16401.master.patch</li> <li>the patman/ subdirectory,</li> <li>patman contains a program patman/patchsplit.py for splitting 16401.master.patch in to “smaller” patches (currently 30)</li> <li>patman/poemposter.py which performs automatic upload of the “smaller” patches to the webkit bugtracker. it MUST be used with care. you can read about it here: https://lists.webkit.org/pipermail/webkit-dev/2009-August/009374.html</li> </ul> = get test environment set up = the third thing is to get webkit-glib and pywebkitgtk compiled, and get pyjamas-desktop up-and-running with it. that’s absolutely essential: it’s the only way that you can test the full glib/gobject bindings in any way. i would also recommend to the reviewers that they also take the time to get the full test environment up-and-running: it will help in your understanding of where the bindings actually come from. = obtain latest webkit svn = the fourth thing is to obtain the latest svn of webkit, which i strongly recommend, from experience, to use git-svn rather than just svn (you can google “git-svn HOWTO” to find out how to use it). the 16401.master.patch from 2) should then apply cleanly – if not, contact me, and i’ll do some updates. = things to do = things which need to be organised: <ul> <li>a publicly accessible wiki, to coordinate things (in a way that it is well-known that mailing lists and bugtrackers cannot cope with, alone)</li> <li>a publicly available discussion forum</li> <li>a publicly available revision control system [a branch of webkit svn would absolutely be the most ideal scenario]. i’m quite happy for the revision control system to be github.com except for the fact that revision history is then lost (to the webkit svn)</li> </ul> = build of webkit instructions = do a git clone of the repository (on github): <pre><code> git clone git://github.com/lkcl/webkit.git </code></pre> then, to check out branch 16401.master, run the following commands: <pre><code> cd webkit git checkout -b 16401.master origin/16401.master </code></pre> then you are ready to build: <ul> <li>mkdir build</li> <li>cd build</li> <li>../autogen.sh —prefix=/usr</li> <li>make -j2</li> <li>sudo make install</li> </ul> = get pywebkitgtk and patch it = <ul> <li>svn checkout http://pywebkitgtk.googlecode.com/svn/trunk/ pywebkitgtk-read-only</li> <li>cd pywebkitgtk-read-only</li> <li>download attachment from http://code.google.com/p/pywebkitgtk/issues/detail?id=13</li> <li>patch < {filename}</li> <li>./autogen.sh —prefix=/usr.</li> <li>make</li> <li>sudo make install</li> </ul> = installing pyjamas = To test the above, you’ll need pyjamas-desktop: <pre><code> svn co https://pyjamas.svn.sourceforge.net/svnroot/pyjamas/trunk pyjamas cd pyjamas python bootstrap.py sudo python run_bootstrap_first_then_setup.py install </code></pre> To run a test example: <pre><code> cd examples/helloworld python Hello.py </code></pre> 2010-02-09T19:10:29-08:00 294450 helping-with-16401master

53725

2009-08-18T06:45:04-07:00

10158