Getting Started With Open Source

Transcript

1. Open Source Manoj M J GETTING STARTED WITH
2. Let’s Talk About Open Source Benefits of contributing to Open Source Myth-busting, FAQs How to contribute My journey in the Open Source world
3. What is open source? “denoting software for which the original source code is made freely available and may be redistributed and modified.”
4. What do I gain? Deeper understanding of the technology Build your reputation (and your Resume!) As a company, build better workforce and attract top talent.
5. Sounds interesting, but…
6. I’ve just started my career and I have no idea about the open source world… Blocker
7. Y’all need just Git + GitHub Look for beginner-friendly issues Cultivate the habit of “reading code” The community is super-friendly No different from making a PR at work
8. I need to be a programmer to contribute to Open Source.. Myth
9. Documentation! ( easiest way to get started!) Make a difference, just by editing! Raise bug reports aka Issues! Contribute art and logos! https://github.com/Netflix/fast_jsonapi/issues/344 https://github.com/rails/rails/pull/32735 https://github.com/django/django/pull/2692 Pro-tip: Issues also count towards your open source contribution! https://contributors.rubyonrails.org/
10. The quality of code in open-source repos is top notch. I’ll never be able to code in the way they do! Blocker
11. Even the masters have trouble getting started! Just embrace the worst case scenario! Fear not, coz test suit got you covered! https://github.com/rails/rails/pull/11168 https://github.com/ruby/ruby/pull/10
12. But.. I need to write tests! Blocker
13. Test suites are (almost always) already set No way around this :( Build around existing tests!
14. It’s easy. It’s doable. But you need: Persistence & Patience. Open source Contributions
15. My Journey
16. Started from here: Never used git or Github for code sharing before 1st job. Shared code on Dropbox between team- mates
17. ACTUAL IMAGE FROM MY ACTUAL COLLEGE PROJECT!!!
18. MY FIRST PR! https://github.com/rails/rails/pull/24782
21. YOU MAD BROO??
22. Maintainer’s Reaction
23. MY FIRST PR! ..was rejected in under 40 minutes!
24. Persistence & Patience Kept reading code Always looked out for opportunities to make tiny changes
25. Rails Netflix FastJson API Facebook Messenger Gem Bugsnag-ruby
26. But, I still do stupid things…
27. Raises issue to Sidekiq…
28. Aaandddd…. It’s closed!
29. But stupidity is okay in OSS…
30. If you don’t ask The answer is always NO
31. If you don’t raise a PR you will never know!
32. Moving towards your first contribution
33. Subscribe to repos you are interested in.
34. Documentation is the absolute best place to start! Documentation is often neglected by the maintainer. No need to write tests! WIN! Tiny changes, hence easier to get started. Low effort, high impact Helps build rapport with the maintainer
35. Look for beginner friendly labels in repos.
36. When you face trouble in day-to-day work, don’t hesitate to create an issue or raise a PR!
38. Don’t fear the community They are here to help
39. (Only) the first PR is the hardest!
40. Questions? Thanks!