![[ how did we meet
with Marcus D.? ]](https://image.slidesharecdn.com/1-2019-esug-learningbydoing-191104142049/85/Learning-by-contributing-to-Open-Source-Software-27-320.jpg)
![[ we reviewed squeak
bug issues ]](https://image.slidesharecdn.com/1-2019-esug-learningbydoing-191104142049/85/Learning-by-contributing-to-Open-Source-Software-28-320.jpg)
![[ Free side effect ]
When you contribute to open-source you
improve your visibility](https://image.slidesharecdn.com/1-2019-esug-learningbydoing-191104142049/85/Learning-by-contributing-to-Open-Source-Software-37-320.jpg)
![[ Remember ]
Every thing you do today has an impact
on your tomorrow!](https://image.slidesharecdn.com/1-2019-esug-learningbydoing-191104142049/85/Learning-by-contributing-to-Open-Source-Software-38-320.jpg)
![[Personal note]
• My objective is to read (and understand) all Pharo source
code :)
• So I take any opportunity to read code
• I even read closed issues](https://image.slidesharecdn.com/1-2019-esug-learningbydoing-191104142049/85/Learning-by-contributing-to-Open-Source-Software-39-320.jpg)
Learning by contributing to Open-Source Software
- 1. Learning by contributing to Open-Source Software stephane.ducasse@inria.fr https://github.com/pharo-project/pharo
- 2. z. zidane
- 5. r. federer
- 11. Did you see the pattern?
- 12. How to practice software skills?
- 13. How to practice software skills? • Program (but how to get feedback) code reviews are precious but difficult to get • Code katas (always fun) • Participate to sprints - Pair program • Participate to open-source
- 14. But I’m a noob
- 15. And the world is complex
- 16. Wait wait wait…
- 17. We are all noobs!
- 18. The solution is just some clicks away…
- 19. Take any opportunity to read code
- 20. Take any opportunity to contribute
- 21. Contributing is easy & simple
- 22. Possible contributions • Read/answer newbie questions • Participate to the wiki • Review bug entry description • Review bug fixes • Write tests for bug entries • Improve test coverage • Improve comments
- 23. Newbie Questions • I learned a lot answering them :) • When I did not know I looked for the answers • Try and learn
- 24. Read discord
- 25. Answer questions • On discord • Mailing-list
- 26. Take any opportunity to contribute
- 27. [ how did we meet with Marcus D.? ]
- 28. [ we reviewed squeak bug issues ]
- 29. Bug issue contribution • Can you understand it? • else ask for precision • Can you repeat the problem mentioned? • report it. This is a valuable information
- 30. Bug issue contribution •Write a test to show the problem? •If the contributor provides a test, is it sounds?
- 32. What if you do not know? What if you do not understand?
- 33. Easy! Drop it and pick the next one
- 34. Read tests to learn • Tests are cool to learn • Tests can be improved, so you can improve them
- 35. Improve test coverage • It is often easier to write tests than the code :) • Grab an object and inspect it • Turn this in a test
- 37. [ Free side effect ] When you contribute to open-source you improve your visibility
- 38. [ Remember ] Every thing you do today has an impact on your tomorrow!
- 39. [Personal note] • My objective is to read (and understand) all Pharo source code :) • So I take any opportunity to read code • I even read closed issues
- 40. Do not miss a great opportunity to grow your knowledge Join and invent the future