Sreeja Kamishetty
unread,Oct 25, 2021, 2:58:01 PM10/25/21Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Chromium GSoC'21, Chromium GSoC'21 Admins, nirj...@gmail.com, srnikh...@gmail.com, riya...@gmail.com, coder.n...@gmail.com, shashv...@gmail.com, inbox...@gmail.com, hantanuch...@gmail.com, omdha...@gmail.com, thisisa...@gmail.com, yuvi...@gmail.com, aarya...@gmail.com, nbhat...@gmail.com, risha...@outlook.com, kushals...@gmail.com, dhruv.si...@gmail.com, devanapall...@gmail.com, udayrath...@gmail.com, ajaa...@gmail.com, sardan...@gmail.com, v.cy...@gmail.com, ashuto...@gmail.com, sharmahr...@gmail.com, ujaulk...@gmail.com, tusharchop...@gmail.com, oberon...@gmail.com, kunalgu...@gmail.com, tanujsh...@gmail.com, dhruvrajsin...@gmail.com, nishi...@gmail.com, aadilkh...@gmail.com, vaibhav...@gmail.com, sammahe...@gmail.com, kushwa...@gmail.com, amog...@gmail.com, pratikhal...@gmail.com, roy...@gmail.com, nilabhroc...@gmail.com, rajkotiya...@gmail.com, f202...@pilani.bits-pilani.ac.in, 1sanjee...@gmail.com, roshanm...@gmail.com, pratiy...@gmail.com, harshc...@gmail.com
Hi Everyone,I hope you all are well. We are so happy to see your interest and passion in contributing to Chromium to make the web better for billions of users worldwide.To help you get started with chromium development. I will share a few steps below. If you have any questions, please post your queries to this channel, and we will get them answered.Setup Chromium
Chrome is huge. Recommended machines for the build are 64-bit O.S. with at least 8GM of RAM (more the merrier) and 1000 GB of free disk space. You can find OS-specific instructions on building Chromium, and please don't miss any steps.Find/ File something to work on - https://crbug.com
Suppose you find any bug in the available list you are interested in working on it. Add a comment to get it assigned. One of the suggested ways to start is to look into good first bugs and send a fix for them.
The component field specifies the area of the work. You could look into these groups if you are interested in exploring issues specific to different areas, e.g., Accessibility, CSS, navigation, and many others.
Search and Browse the code
Chromium code search is our best friend, which helps us navigate the codebase, find references, code specific to languages (JS, Java, C++, e.t.c).
P.S I use Chrome code search more than google search here.
Create change and Send your code for review
If you are ready with the fix. Give a pat on your back. You did great. Now time to send it to review and land your fix. Chromium has a style guide, don't forget to check it before sending.
Create a local branch for fix: git checkout -b my_branch_name -t origin/main
Add your code: git add. && git commit -m "my commit"
Upload your code: git cl upload and write a summary for your change.
If you are not familiar with git, don't worry. These resources will help you.
More Documentation
Contributing to Chromium, Developer guide, Chromium docs, Chromium OS docs, Chrome University Videos.Once you become a regular contributor and start landing code, we will provide you GOMA, try job access to speed up your build.Still worried and looking for mentorship or help?If you are still stuck and don't know what to do, email me. I can't assure you that I will know the answer, but I will add people who can help and guide you with the problem. I might not reply immediately, but please wait I will get back.I am currently working on Multi Page Architecture, and if you would like to work on it. I would be happy to mentor you. Please see the available issues here and let me know if you want to work on them.
Stay tuned for announcements on Google Summer of Code 2022. Once again, thank you and we look forward to seeing your contributions!
Best Regards,
Sreeja - Chromium GSoC Admin.