On Tue, Apr 30, 2013 at 1:19 AM, <[email protected]> wrote:

> Hello!
>
> "thanks for your interest! Is there anything in particular that would
> interest you, and/or do you already have any concrete ideas what you'd like
> to work on?"
>
>    Honestly, I was interested in trying out a Google Open Source project,
> so am wide open to ideas.  :-)
>

Unfortunately we don't have a list of things that need doing and are
suitable for beginners. V8 has a pretty steep learning curve, and working
on most of the interesting problems requires a couple of months of
experience.

One easy thing that you could do to get warmed up is to implement
FLAG_trap_on_deopt on non-ia32 architectures. Once you have figured out
what to do there, the actual change should be rather trivial. (I'm not
giving you any more concrete hints on purpose; use this as an opportunity
to dig around the code base on your own.)

You'll probably also want to look at some introductory documentation.
There's no official, complete documentation (besides the code ;-) ), but
some of the videos and design docs on v8.googlecode.com are still very
relevant, and there are pretty good blog posts at wingolog.org and
floitsch.blogspot.com.

"Have you already checked out V8 and compiled it?"
>
>    Yes.  I have also run the shell.exe application.
>

Great. Note that we use d8 for development purposes, which is a bit more
powerful than the shell.


> "Working on Windows is possible, but comparatively painful. Linux would
> make your life a lot easier."
>
>    Maybe I can start with Windows, since I don't have a Linux machine.   I
> will certainly strongly consider it based on your advice!
>

Sure, as I said, working on Windows is certainly possible (but nobody on
the team is doing it, because it just makes life too hard). If you don't
want to get into the business of using virtual machines or partitioning
your hard drive for dual-booting, you can actually install Ubuntu into a
big file on your Windows hard drive (
http://www.ubuntu.com/download/desktop/install-ubuntu-with-windows). 20GB
or so should be plenty to get you going.


>
> Regards,
> ...John
>
>
> On Monday, April 29, 2013 7:23:02 AM UTC-5, Jakob Kummerow wrote:
>
>> Hi,
>>
>> thanks for your interest! Is there anything in particular that would
>> interest you, and/or do you already have any concrete ideas what you'd like
>> to work on?
>>
>> Have you already checked out V8 and compiled it?
>>
>> Working on Windows is possible, but comparatively painful. Linux would
>> make your life a lot easier.
>>
>> Cheers,
>> Jakob
>>
>>
>> On Sat, Apr 27, 2013 at 7:59 PM, <[email protected]> wrote:
>>
>>> Hello!
>>>
>>> I'm a C++ programmer and would like to help contribute to V8.   I'm on a
>>> Windows 7 machine.
>>>
>>> On the "contributor" page, https://code.google.com/**
>>> p/v8/wiki/Contributing <https://code.google.com/p/v8/wiki/Contributing>,
>>> it says:
>>>
>>>  "Before you start working on a larger contribution V8 you should get
>>> in touch with us first through the V8 contributor mailing 
>>> list<http://groups.google.com/group/v8-dev> so
>>> we can help out and possibly guide you; coordinating up front makes it much
>>> easier to avoid frustration later on."
>>>
>>> So, I hope to get some feedback here on what may be needed!    I've done
>>> a lot of coding and designing, mostly in C++, but also in C#, ActionScript
>>> (Flex), and  various other scripting languages, including JavaScript.    I
>>> have even done some work in designing my own interpreter.
>>>
>>> Thanks for any feedback!  :-)
>>>
>>> Regards,
>>> John Alway
>>>
>>>
>>>
>>

-- 
-- 
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- 
You received this message because you are subscribed to the Google Groups 
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to