Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Contributing to Pharo

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Nächste SlideShare
ShowUs: Improved DoIt
ShowUs: Improved DoIt
Wird geladen in …3
×

Hier ansehen

1 von 45 Anzeige

Weitere Verwandte Inhalte

Aktuellste (20)

Anzeige

Contributing to Pharo

  1. 1. Contributing to Pharo: Easy, simple, fun and empowering stephane.ducasse@inria.fr https://github.com/pharo-project/pharo
  2. 2. Remember … https://rmod- fi les.lille.inria.fr/Team/Presentations/2019-ESUG-LearningByDoing-Ducasse.pdf
  3. 3. How to practice software skills?
  4. 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. 5. But I’m a noob
  6. 6. And the world is complex
  7. 7. Wait wait wait…
  8. 8. We are all noobs!
  9. 9. The solution is just some clicks away…
  10. 10. Take any opportunity to read code
  11. 11. Take any opportunity to contribute
  12. 12. Contributing is easy & simple
  13. 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. 14. Take any opportunity to contribute
  15. 15. Contribute to Code • Set up your own Pharo fork/Image • Create a branch • Improve Pharo • Commit • PR
  16. 16. Step: Fork the pharo repo
  17. 17. Step one • Fork Pharo repo
  18. 18. Step one • Fork Pharo repo
  19. 19. Step: Grab latest image
  20. 20. Step one • Fork Pharo repo
  21. 21. Step one • Fork Pharo repo
  22. 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. 23. Step: Repair
  24. 24. Step: Repair Now your Pharo image knows where is the code repo
  25. 25. if fetch required, fetch
  26. 26. Remember Iceberg actions are sorted from more likelihood to less likeli hood
  27. 27. Now Now your local get the latest changes (according to the image) from Pharo
  28. 28. Detached Working Copy
  29. 29. Repair Now it will create a branch pointing to the state of your image
  30. 30. Create a “bottom” branch
  31. 31. This way you can always come back “here”
  32. 32. Step: Create a Branch for your fi x
  33. 33. Step: Do your fi x
  34. 34. Step: commit to your fork
  35. 35. Step: Push to your fork
  36. 36. Step: Do a PR
  37. 37. Step: Do a PR
  38. 38. Step: Check out your “bottom” branch • And now you can fi x another one :)
  39. 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. 40. Contributing to Pharo is easy • You will improve Pharo • You will learn a lot • You will meet friends • You will build network
  41. 41. [ Free side effect ] When you contribute to open-source you improve your visibility
  42. 42. [ Remember ] Every thing you do today has an impact on your tomorrow!
  43. 43. [ how did we meet with Marcus D.? ]
  44. 44. [ we reviewed squeak bug issues ]
  45. 45. [ then we created Pharo :) ]

×