Hey 👋 I would like to contribute - where should I focus?

[Tugkan Kibar]

Hey V8 team 👋

I'd like to contribute to V8 - where should I direct my focus to? I've started with https://v8.dev/docs - it was asking me to message here.

I've noticed a message from someone that suggests;

• The best way to start with V8 is to play around "hello world" at https://v8.dev/docs/embed to find out the basics.
  
• Then, https://github.com/thlorenz/v8-perf/blob/master/README.md will give you some links to find out how V8 works internally
  
• https://v8.dev/docs will explain some workflows to use.
  

Which makes sense regarding some ways to get my hands dirty - however doesn't really explain to me how to find a way to contribute to the project & work towards that (e.g. type of errors, good first issues etc.)

Could you please provide me some guidance on this?

[Jakob Kummerow]

Some bugs are labeled "HelpWanted": https://bugs.chromium.org/p/v8/issues/list?q=label%3AHelpWanted&can=2

They probably vary a lot in terms of required effort and difficulty.

The label likely hasn't been applied exhaustively, so you can also look at other open bugs. Though keep in mind that many of the older bugs are open for a reason: either they were considered unimportant, or we couldn't think of an acceptable solution, etc. But I'm sure there are some that would benefit from some love :)

Feel free to pick something you find interesting, whether that's performance work or spec compliance issues or engineering productivity (like faster builds and tests) or embedder documentation/samples, etc. 

Note that ramping up on V8 is a serious time commitment. Don't get discouraged when it takes a while (and a lot of reading of docs and code) until you feel somewhat familiar.

--