Go beyond "composer update", contribue!

Go beyond "composer update", contribue!

6baa34bc1e5c347b1003f6abe8691de1?s=128

Nicolas Grekas

December 02, 2016
Tweet

Transcript

  1. Go beyond composer update Contribute!

  2. Fork symfony/symfony

  3. ./phpunit src/Symfony

  4. Do your magic

  5. ./phpunit src/Symfony/Component/Debug

  6. Pull requests template

  7. Features and deprecations must be submitted against the master branch

  8. Bug fixes must be submitted against the lowest branch where

    they apply
  9. Lowest branches are regularly merged to upper ones so they

    get the fixes too
  10. Branch merging

  11. Add a description of what your PR is solving Help

    yourself by helping others
  12. None
  13. Congratulations!

  14. Community triage Please wait…

  15. Fix your base branch

  16. Mind your commit message Commits are squashed

  17. Cover with unit tests

  18. Welcome comments There is nothing personal

  19. Feedbacks will make you a better developer It’s a matter

    of POV diversity, not skills
  20. When you don’t care Follow the suggestions

  21. Help yourself by helping others Provide reproducers, insights, etc. Have

    empathy
  22. But I don’t know where to start?

  23. Look at recent issues first Many already looked at old

    issues so they must be hard
  24. • Every month: a bugfix release • Every 6 month:

    a feature-set release • Every 2 years: a squeezed out release
  25. • Every month: a bugfix release • Every 6 month:

    a feature-set release • Every 2 years: a squeezed out release Symfony 4.0 is in exactly 1 year!
  26. Go beyond composer update Let’s practice tomorrow!