You Should Be An Open Source Developer

My talk from BrnoPHP about Open Source Philosophy and how it can boost your career and make you a better person & developer.

Transcript

1. You should be
   an developer
   BrnoPHP, 14th November 2015 in Brno, Czech Republic
   

   View Slide

2. Paweł Jędrzejewski
   I really like Open Source
   I created Sylius
   I co-founded Lakion
   I help organize PHPers Łódź
   

   View Slide

3. Sylius
   E-Commerce PlaKorm for PHP
   MIT License
   

   View Slide

4. 245+ Code contributors
   1,350,000+ Downloads
   430 Translators
   Alpha running in production
   first bits of code in 2011
   1.0.0 due next year
   

   View Slide

5. ?
   @pjedrzejewski
   What is Open Source?
   

   View Slide

6. OSS
   @pjedrzejewski
   There is free so8ware.
   And there is Open Source
   Philosophy.
   

   View Slide

7. ?
   @pjedrzejewski
   Why you should do (more)
   Open Source?
   

   View Slide

8. @pjedrzejewski
   Learning.
   

   View Slide

9. @pjedrzejewski
   InnovaWon takes place in Open
   Source.
   Best PracWces emerge from OS.
   

   View Slide

10. @pjedrzejewski
    Enrich your developer
    toolset!
    

    View Slide

11. @pjedrzejewski
    Code Review & Mentoring
    =
    Learning by sharing your
    knowledge.
    

    View Slide

12. @pjedrzejewski
    Team work and distributed
    workflow.
    

    View Slide

13. @pjedrzejewski
    Experience - easy to get!
    Learning from others
    Good starWng point for young developers
    InteresWng addiWon to your CV
    

    View Slide

14. @pjedrzejewski
    Earning reputaWon and
    gaining visibility.
    

    View Slide

15. good
    @pjedrzejewski
    Making connecWons.
    

    View Slide

16. great
    @pjedrzejewski
    Making friends.
    

    View Slide

17. @pjedrzejewski
    Giving back to the
    community. Feels good.
    

    View Slide

18. ?
    @pjedrzejewski
    How to start?
    

    View Slide

19. @pjedrzejewski
    Every contribuWon is
    important and valuable.
    

    View Slide

20. @pjedrzejewski
    A suggesWon or an idea can
    someWmes be more
    valuable than a code patch.
    

    View Slide

21. @pjedrzejewski
    TesWng and bug reports. Yes,
    please!
    Especially on Windows.
    

    View Slide

22. Documentation is as important as code.
    

    View Slide

23. @pjedrzejewski
    Code patches. Simple.
    

    View Slide

24. workflow
    1. Fork on GitHub.
    $ git clone git@github.com:/symfony.git
    $ cd symfony
    $ git co -b fix-discounts-bugs
    2. Change what you need to fix it.
    $ git commit -m „Fixed bug when coupon is null”
    $ git push origin fix-discount-bugs
    3. Open a PR on GitHub.
    @pjedrzejewski
    

    View Slide

25. @pjedrzejewski
    Start blogging.
    

    View Slide

26. @pjedrzejewski
    Provide support for the users.
    Sign-up for the mailing list or join the
    IRC. Check quesWons on StackOverflow.
    

    View Slide

27. @pjedrzejewski
    Help with maintenance.
    Check github issues, review PRs.
    

    View Slide

28. @pjedrzejewski
    Talk about a project at
    your local PHP meet up.
    

    View Slide

29. @pjedrzejewski
    But it only works if I
    create a popular
    project… ;(
    

    View Slide

30. @pjedrzejewski
    You can join an exisWng project.
    Trust me, they are looking for you.
    

    View Slide

31. From hero to hero
    Lead maintainer
    Co-maintainer
    AcWve contributor
    One Wme contributor
    @pjedrzejewski
    

    View Slide

32. Yes, it is not that perfect.
    Downsides
    @pjedrzejewski
    

    View Slide

33. Open Source takes Wme.
    Very ofen, your free Wme.
    

    View Slide

34. View Slide

35. „I get hate mail for hacking on Open Source.
    People have started mulWple "peWWons" on
    peWWon web sites, asking me to stop working
    (google for it). Recently, people started
    collecCng Bitcoins to hire a hitman for me
    (this really happened!).”
    Source: hkps:/
    /plus.google.com/+LennartPoekeringTheOneAndOnly/posts/J2TZrTvu7vd
    

    View Slide

36. ?
    @pjedrzejewski
    Scared? Don’t be. It is
    great fun.
    

    View Slide

37. @pjedrzejewski
    Tips for starting your own project
    Show of your idea as soon as you get MVP
    StarWng documenWng from day one
    Good test suite will be your best friend
    Create a team from acWve contributors
    Organize community work, set a roadmap
    

    View Slide

38. ?
    @pjedrzejewski
    How to moneWze your Open
    Source work? Everyone needs
    to eat and pay bills…
    

    View Slide

39. @pjedrzejewski
    Become a consultant or
    freelance developer. Organize
    trainings/workshops.
    

    View Slide

40. @pjedrzejewski
    Use Open Source
    bounWes and donaWons.
    

    View Slide

41. PLEASE DONATE VIA
    

    View Slide

42. @pjedrzejewski
    Build a business around
    your OS product.
    Hard
    

    View Slide

43. @pjedrzejewski
    Sell services:
    development, consulWng
    and training.
    

    View Slide

44. @pjedrzejewski
    Partner, cerWficaWon
    and support programs.
    

    View Slide

45. View Slide

46. @pjedrzejewski
    Theme and plugin
    markets.
    

    View Slide

47. View Slide

48. View Slide

49. @pjedrzejewski
    Hiring ProWp: Good Open
    Source product akracts
    and retains talents.
    

    View Slide

50. to be continued
    @pjedrzejewski
    

    View Slide

51. !!!
    @pjedrzejewski
    Rule #1. Don’t be shy.
    Accept construcWve criWcism
    and improve on that.
    

    View Slide

52. !!!
    @pjedrzejewski
    Rule #2. Be nice and remember
    that there is a person behind
    the GitHub nickname.
    

    View Slide

53. !!!
    @pjedrzejewski
    Rule #3. Just start and you will be addicted.
    Trust me again.
    NoWce burnout quickly and you will be fine.
    

    View Slide

54. @pjedrzejewski
    JUST DO IT!
    

    View Slide

55. @pjedrzejewski
    @Sylius
    @Lakion
    pjedrzejewski.com
    sylius.org
    lakion.com
    THANK YOU!
    

    View Slide