Hi Alexander, thank you for your interest in V8. We very much welcome everyone who is willing to spend time on making V8 better. However, since V8 is a rather demanding project, as you may already have noticed, most people working on V8 that I'm aware of do that full-time.
It is true that documentation is some what lacking, and parts of V8 are evolving at a fast pace, making it hard to dive right into it. I think the best approach to get familiar with V8 is to study the embedder's guide<https://developers.google.com/v8/embed> to get a feel about how V8 works from the API perspective, and gradually work towards the V8 internals from there (for example retrace what happens when a piece of javascript code is fed to V8 to compile and run). Generally speaking, small patches that fix bugs or peephole optimizations here and there (that have real performance impact) are more likely to be accepted and committed to V8 than large overhauls and refactorings. So before you start anything big, it's probably best to get a second opinion lest you get disappointed that we don't accept your patch. Cheers, Yang On Thu, Aug 16, 2012 at 2:42 PM, Alexander Rojas <[email protected]>wrote: > Hi guys, > > I've been wanting to join this project for a time but I never found time > to the tedious task of getting to read documentation and getting to know > the code; however I just got surgery and I've been sitting at home without > much to do during the next week so I thought I might get use this free time > to do this tedious tasks with the hope to be a contributor in the future. I > just would like to know, or to be guided on how to start, where to look and > so on. > > Thanks, > > Alex > > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
