Next round of Outreachy has started from September 12, 2016. I usually get lot of mails and messages through social networking sites regarding Outreachy and generally for the contribution to Linux Kernel. I worked as an Outreachy intern in Round 10 and last summer I also worked as a GSoC mentor under the Linux Foundation. GSoC project I mentored was also related to Linux Kernel. So, I guess it is probably right time to give few tips to prospective applicants of the next Outreachy round. Some of these tips also applies to every newbie who wants to contribute to Linux Kernel.
- Start early so that you have enough time to understand how community works in general and to decide which projects you are interested in.
- Do not hesitate to ask questions. But keep in mind that mentors also expect you to do some sort of search before asking a question. So, it is important to understand what questions to ask. The paper How To Ask Questions The Smart Way by Eric Raymond and Rick Moen is an excellent guide.
- Take mentors’/reviewers’/maintainers’ comments positively. And work on them to avoid repeating same mistakes again. Also, learn from others’ mistakes. I am still used to read comments of developers on others’ patches so that I don’t repeat the same mistake in my patch. I followed the same rule during my application round as well. So, read comments of mentors on other applicants’ patches and try to follow them as well.
- If something is not clear in the comment then please ask. It is better to ask at that time than repeating the same mistake again. This will save your time.
- Be nice and respect others’ point of views. Definitely we like to discuss on technical parts but arguing politely will help you to create bonding and it is necessary for the healthy community as well.
- The culture in a particular open source community may vary from that in other communities. Kernel community is famous for their frank opinions. Generally the comments on your patch is for your code or the change you are proposing, and not for the person as an individual. So,never take those comments personally. Take them positively and try to improve the quality of code for the next contribution.
- Engage in community. We like when applicants helps each other. Never look at this as a competition. In the end, we all are going to learn something. This is true for both mentors and applicants.
Kernel contribution or patch related tips:
- First kernel patch tutorial is your friend. This includes everything from installing things to sending your patches properly. Read it very carefully.
- Usually in Outreachy we advise applicants to start from checkpatch.pl issues just to give them an idea about how community works and to help them get started with contributing to the Linux Kernel. But not every checkpatch.pl warning/error is right. So please try to understand why that warning is there instead of fixing them blindly. There are false positives as well.
- Do not top post while responding to mails. Look at the details of how to respond to mails inline.
- Do not copy commit log and subject. You can check the other patches for the reference but copy pasting will never help.
- For the subject line always run ‘git log’ to check what kind of subject lines are used for the particular file.
- Quantity of patches matters but quality of patches is important as well. Move from checkpatch.pl issues once you get the idea of how things are working. This will help you to learn more.
- Usually in the Linux kernel projects, we have small tasks for the applicants by mentors. Work on them and ask questions to mentors if something is not clear.
- Be consistent in sending patches. Being in touch with the mentors help them to understand your perspective for the project.
- Two important things to do before sending every patch:
- Always compile-test your patch before sending it to the maintainers/mailing lists.
- Always run checkpatch.pl on your patch.
Half of the time this will show you if your change is correct or not.
Application related tips:
- Never lie about your commitments for the internship period. Be clear and discuss this with mentors of the project you are applying.
- Mention about what kind of work you have done and how this will help you achieve your goal in the project. The point of mentioning this tip here is, you can have idea about what kind of patches you should send during the application period.
Last but not least, always remember that we all were newbie at one point of time. So, never feel embarrassed or bad when something is not working. You are amazing and we are thankful to you as you are helping us to improve our community or code or even ourselves as well.