![[ Free side effect ]
When you contribute to open-source you
improve your visibility](https://image.slidesharecdn.com/02-2022-esug-contributetopharo-ducasse-220928130529-906817b0/85/Contributing-to-Pharo-41-320.jpg)
![[ Remember ]
Every thing you do today has an impact
on your tomorrow!](https://image.slidesharecdn.com/02-2022-esug-contributetopharo-ducasse-220928130529-906817b0/85/Contributing-to-Pharo-42-320.jpg)
![[ how did we meet
with Marcus D.? ]](https://image.slidesharecdn.com/02-2022-esug-contributetopharo-ducasse-220928130529-906817b0/85/Contributing-to-Pharo-43-320.jpg)
![[ we reviewed squeak
bug issues ]](https://image.slidesharecdn.com/02-2022-esug-contributetopharo-ducasse-220928130529-906817b0/85/Contributing-to-Pharo-44-320.jpg)
![[ then we created
Pharo :) ]](https://image.slidesharecdn.com/02-2022-esug-contributetopharo-ducasse-220928130529-906817b0/85/Contributing-to-Pharo-45-320.jpg)
Contributing to Pharo
- 1. Contributing to Pharo: Easy, simple, fun and empowering stephane.ducasse@inria.fr https://github.com/pharo-project/pharo
- 3. How to practice software skills?
- 4. How to practice software skills? • Program (but how to get feedback) code reviews are precious but di ffi cult to get • Code katas (always fun) • Participate to sprints - pair program • Participate to open-source
- 5. But I’m a noob
- 6. And the world is complex
- 8. We are all noobs!
- 9. The solution is just some clicks away…
- 10. Take any opportunity to read code
- 11. Take any opportunity to contribute
- 12. Contributing is easy & simple
- 13. Possible contributions • Read/answer newbie questions • Participate to the wiki • Review bug entry description • Review bug fi xes • Write tests for bug entries • Improve test coverage • Improve comments
- 14. Take any opportunity to contribute
- 15. Contribute to Code • Set up your own Pharo fork/Image • Create a branch • Improve Pharo • Commit • PR
- 16. Step: Fork the pharo repo
- 17. Step one • Fork Pharo repo
- 18. Step one • Fork Pharo repo
- 19. Step: Grab latest image
- 20. Step one • Fork Pharo repo
- 21. Step one • Fork Pharo repo
- 22. Situation • The image has code too • The local and remote repo can be desynchronized • The image and local repo can be desynchronized local repository remote repository image git working copy
- 23. Step: Repair
- 24. Step: Repair Now your Pharo image knows where is the code repo
- 25. if fetch required, fetch
- 26. Remember Iceberg actions are sorted from more likelihood to less likeli hood
- 27. Now Now your local get the latest changes (according to the image) from Pharo
- 29. Repair Now it will create a branch pointing to the state of your image
- 30. Create a “bottom” branch
- 31. This way you can always come back “here”
- 32. Step: Create a Branch for your fi x
- 34. Step: commit to your fork
- 35. Step: Push to your fork
- 36. Step: Do a PR
- 37. Step: Do a PR
- 38. Step: Check out your “bottom” branch • And now you can fi x another one :)
- 39. No need to refork or sync your repo • Do not care if your fork is not up to dat • When you will do the fetch, your local will be updated (from latest Pharo) • When you will push to your remote, your local will send the latest Pharo change there
- 40. Contributing to Pharo is easy • You will improve Pharo • You will learn a lot • You will meet friends • You will build network
- 41. [ Free side effect ] When you contribute to open-source you improve your visibility
- 42. [ Remember ] Every thing you do today has an impact on your tomorrow!
- 43. [ how did we meet with Marcus D.? ]
- 44. [ we reviewed squeak bug issues ]
- 45. [ then we created Pharo :) ]