Open Source: When Nights & Weekends Are Not Enough

How to contribute to open source projects during your work week. Tips for maintainers, contributors, and managers to bake in contributions in your day-to-day workflow.

Presented at Southeast Ruby 2-17.

Transcript

1. Open Source: When Nights & Weekends Are Not Enough Southeast Ruby, October 2017
2. Ernesto Tagwerker @etagwerker
3. Founder & Software Engineer at Ombu Labs
4. Open Source Contributor & Maintainer
5. Father & Husband at Home
6. Open Source & Parenting 6
7. Open Source & Lack of Time 7
8. 2. What is a contribution? 8 1. Pre-Parenting vs. Post-Parenting 3. Tips for Contributors, Maintainers, & Managers
9. 2. What is a contribution? 9 1. Pre-Parenting vs. Post-Parenting 3. Tips for Contributors, Maintainers, & Managers
10. 2. What is a contribution? 10 1. Pre-Parenting vs. Post-Parenting 3. Tips for Contributors, Maintainers, & Managers
11. Pre-Parenting vs. Post-Parenting 11
12. Pre-Parenting
13. Open Source: Every Night 13
14. Open Source: Entire Weekends 14
16. Post-Parenting
17. Open Source: Every Night Some Nights 17
18. Open Source: Entire Weekends Some Weekend Nights 18
19. Open Source: At Work 19
20. “Using and contributing to open source often happens on the job” (Open Source Survey 2017)
21. What is an open source contribution anyway?
22. Submitting a new issue 22
23. Submitting a pull request 23
24. Creating an open source project 24
25. According to Github
26. Other ways to contribute
27. Adding additional info to an existing issue 27
28. Proposing a workaround 28
29. Answering a question in Stack Overflow 29
30. Contribution: Adding value to an open source project
31. 1. Contributors
32. 1. Contributors 2. Maintainers
33. 1. Contributors 2. Maintainers 3. Managers
34. 8 Tips for Contributors
35. 35 Bake in open source contributions in your workflow 1
36. A Workflow Without Contributions
37. 1. Use open source library 37 2. Find issue 3. Do research The Usual Workflow 4. Found new bug 5. Apply solution 6. Move on to next problem
38. 1. Use open source library 38 2. Find issue 3. Do research The Usual Workflow 4. Found new bug 5. Apply solution 6. Move on to next problem
39. 1. Use open source library 39 2. Find issue 3. Do research The Usual Workflow 4. Found new bug 5. Apply solution 6. Move on to next problem
40. 1. Use open source library 40 2. Find issue 3. Do research The Usual Workflow 4. Found new bug 5. Apply solution 6. Move on to next problem
41. 1. Use open source library 41 2. Find issue 3. Do research The Usual Workflow 4. Found new bug 5. Apply solution 6. Move on to next problem
42. 1. Use open source library 42 2. Find issue 3. Do research The Usual Workflow 4. Found new bug 5. Apply solution 6. Move on to next problem
43. A Workflow With Contributions
44. 1. Use open source library 44 2. Find issue 3. Do research A Workflow With Contributions 4. Found new bug … 5. Submit a new issue 6. Submit a pull request (or not!)
45. 1. Use open source library 45 2. Find issue 3. Do research A Workflow With Contributions 4. Found new bug 5. Submit a new issue 6. Submit a pull request (or not!) …
46. 1. Use open source library 46 2. Find issue 3. Do research A Workflow With Contributions 4. Found new bug 5. Submit a new issue 6. Submit a pull request (or not!) …
47. 47 … A Workflow With Contributions 4. Found new bug 7. Apply solution 8. Move on to next problem 5. Submit a new issue 6. Submit a pull request (or not!)
48. 48 2 bundle open & byebug are your friends
49. 49 3 When you submit an issue include all your research
51. 51 4 Submit small pull requests
53. 53 5 Keep up with the latest versions
55. 55 6 Solve every problem as if your code were to be open sourced
56. For example: As a Developer I want to be able to print official invoices in Argentina
57. 57 https://github.com/ombulabs/afip_bill
58. 58 7 Contribute with something you are passionate about
60. 60 https://github.com/etagwerker/rtopsy
62. Sorry!
64. Yes!
65. 65 8 Reach out to open source developers
66. database_cleaner & email-spec
67. 2 Tips for Maintainers
68. 68 1 Be responsive
71. 71 2 Actively search for co-maintainers
72. database_cleaner & email-spec
73. 2 Tips for Managers
74. 74 1 Encourage your team members to make contributions
75. 75 2 Recurring open source days (e.g. Open Source Fridays)
76. Invest time contributing to open source
77. Thank you! @etagwerker 77
78. Resources 78 1. http://opensourcesurvey.org/2017/ 2. https://github.com/plataformatec/simple_form/issues/1503 3. https://github.com/plataformatec/simple_form/pull/1504 4. https://github.com/dear-github/dear-github 5. https://github.com/pickhardt/maintainers-wanted 6. https://www.codetriage.com 7. https://github.com/departurerb/departure/pull/13 8. https://github.com/ombulabs/afip_bill/ 9. https://github.com/etagwerker/rtopsy 10. https://github.com/pengwynn/topsy