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
2. Paweł Jędrzejewski I really like Open Source I created Sylius I co-founded Lakion I help organize PHPers Łódź
3. Sylius E-Commerce PlaKorm for PHP MIT License
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
5. ? @pjedrzejewski What is Open Source?
6. OSS @pjedrzejewski There is free so8ware. And there is Open Source Philosophy.
7. ? @pjedrzejewski Why you should do (more) Open Source?
8. @pjedrzejewski Learning.
9. @pjedrzejewski InnovaWon takes place in Open Source. Best PracWces emerge from OS.
10. @pjedrzejewski Enrich your developer toolset!
11. @pjedrzejewski Code Review & Mentoring = Learning by sharing your knowledge.
12. @pjedrzejewski Team work and distributed workflow.
13. @pjedrzejewski Experience - easy to get! Learning from others Good starWng point for young developers InteresWng addiWon to your CV
14. @pjedrzejewski Earning reputaWon and gaining visibility.
15. good @pjedrzejewski Making connecWons.
16. great @pjedrzejewski Making friends.
17. @pjedrzejewski Giving back to the community. Feels good.
18. ? @pjedrzejewski How to start?
19. @pjedrzejewski Every contribuWon is important and valuable.
20. @pjedrzejewski A suggesWon or an idea can someWmes be more valuable than a code patch.
21. @pjedrzejewski TesWng and bug reports. Yes, please! Especially on Windows.
22. Documentation is as important as code.
23. @pjedrzejewski Code patches. Simple.
24. workflow 1. Fork on GitHub. $ git clone git@github.com:<user>/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
25. @pjedrzejewski Start blogging.
26. @pjedrzejewski Provide support for the users. Sign-up for the mailing list or join the IRC. Check quesWons on StackOverflow.
27. @pjedrzejewski Help with maintenance. Check github issues, review PRs.
28. @pjedrzejewski Talk about a project at your local PHP meet up.
29. @pjedrzejewski But it only works if I create a popular project… ;(
30. @pjedrzejewski You can join an exisWng project. Trust me, they are looking for you.
31. From hero to hero Lead maintainer Co-maintainer AcWve contributor One Wme contributor @pjedrzejewski
32. Yes, it is not that perfect. Downsides @pjedrzejewski
33. Open Source takes Wme. Very ofen, your free Wme.
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
36. ? @pjedrzejewski Scared? Don’t be. It is great fun.
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
38. ? @pjedrzejewski How to moneWze your Open Source work? Everyone needs to eat and pay bills…
39. @pjedrzejewski Become a consultant or freelance developer. Organize trainings/workshops.
40. @pjedrzejewski Use Open Source bounWes and donaWons.
41. PLEASE DONATE VIA
42. @pjedrzejewski Build a business around your OS product. Hard
43. @pjedrzejewski Sell services: development, consulWng and training.
44. @pjedrzejewski Partner, cerWficaWon and support programs.
46. @pjedrzejewski Theme and plugin markets.
49. @pjedrzejewski Hiring ProWp: Good Open Source product akracts and retains talents.
50. to be continued @pjedrzejewski
51. !!! @pjedrzejewski Rule #1. Don’t be shy. Accept construcWve criWcism and improve on that.
52. !!! @pjedrzejewski Rule #2. Be nice and remember that there is a person behind the GitHub nickname.
53. !!! @pjedrzejewski Rule #3. Just start and you will be addicted. Trust me again. NoWce burnout quickly and you will be fine.
54. @pjedrzejewski JUST DO IT!
55. @pjedrzejewski @Sylius @Lakion pjedrzejewski.com sylius.org lakion.com THANK YOU!