How to contribute to OSS

This is a talk I gave at the CodeCore lunch & learn series about my experience contributing to Rails and other open-source software projects.

Transcript

1. How TO CONTRIBUTE TO OSS   @chancancode
2.   @chancancode
6. YVR
7. How TO CONTRIBUTE TO OSS   @chancancode
8. WHy OSS?
9. Practice Your Craft 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH
10. Practice Your Craft BUILD YOUR RESUME 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
11. Practice Your Craft Build YOUR RESUME MAKE FRIENDS 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
12. PRACTICE YOUR CRAFT BUILD YOUR RESUME MAKE FRIENDS WORK WITH (REALLY) SMART PEOPLE 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
13. PRACTICE YOUR CRAFT BUILD YOUR RESUME MAKE FRIENDS WORK WITH (REALLY) SMART PEOPLE HELP PEOPLE 6. SUBMIT THE PATCH 7. GO TO STEP 4
14. PRACTICE YOUR CRAFT BUILD YOUR RESUME MAKE FRIENDS WORK WITH (REALLY) SMART PEOPLE HELP PEOPLE PAY IT FORWARD 7. GO TO STEP 4
15. HOW DOES OSS WORK?
16. YOU WROTE A PIECE OF CODE 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH
17. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
18. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
19. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
20. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE “Y U NO FIX THIS ALREADY!!!” 6. SUBMIT THE PATCH 7. GO TO STEP 4
21. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE “Y U NO FIX THIS ALREADY!!!” “WHY DID I DO THIS...” 7. GO TO STEP 4
22. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE “Y U NO FIX THIS ALREADY!!!” “WHY DID I DO THIS...” 7. GO TO STEP 4 { WRONG.
23. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE “Y U NO FIX THIS ALREADY!!!” “WHY DID I DO THIS...” 7. GO TO STEP 4
24. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE “Y U NO FIX THIS ALREADY!!!” 6. SUBMIT THE PATCH 7. GO TO STEP 4
25. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
26. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE PEOPLE CONTRIBUTED A PATCH 6. SUBMIT THE PATCH 7. GO TO STEP 4
27. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE PEOPLE CONTRIBUTED A PATCH YOUR CODE GOT BETTER 7. GO TO STEP 4
28. YOU WROTE A PIECE OF CODE YOU DECIDED TO SHARE WITH OTHERS PEOPLE STARTED USING IT PEOPLE FOUND PROBLEMS IN YOUR CODE PEOPLE CONTRIBUTED A PATCH YOUR CODE GOT BETTER EVERYONE IS HAPPY
29. PRACTICE YOUR CRAFT BUILD YOUR RESUME MAKE FRIENDS WORK WITH (REALLY) SMART PEOPLE HELP PEOPLE PAY IT FORWARD 7. GO TO STEP 4
30. PRACTICE YOUR CRAFT BUILD YOUR RESUME MAKE FRIENDS WORK WITH (REALLY) SMART PEOPLE HELP PEOPLE PAY IT FORWARD 7. GO TO STEP 4 { HOW DO I LAND MY FIRST COMMIT IN RAILS? { WHAT CAN I DO FOR THE COMMUNITY?
31. HOW TO LAND YOUR FIRST COMMIT IN #{PROJECT}?
32. LEGACY CODEBASE
33. leg•a•cy code |ˈlegəsē kōd| noun code you didn’t write (this morning)
34. GOOGLE: harry potter legacy codebase
35. AMAZON: WORKING EFFECTIVELY WITH LEGACY CODE
36. REFUSE TO BE DEFEATED
37. DOCUMENTATION
38. FIX A BUG
39. ADD A FEATURE
40. 1. REPRODUCE THE ISSUE 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
41. 1. REPRODUCE THE ISSUE 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
42. 1. REPRODUCE THE ISSUE 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
43. 1. REPRODUCE THE ISSUE 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
44. 1. REPRODUCE THE ISSUE 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
45. 1. REPRODUCE THE ISSUE 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
46. 1. REPRODUCE THE ISSUE 2. IS THIS A BUG? 3. ISOLATE THE PROBLEM 4. COME UP WITH A SOLUTION 5. POLISH 6. SUBMIT THE PATCH 7. GO TO STEP 4
47. COMMUNICATION, COMMUNICATION, COMMUNICATION.
48. NOW WHAT?
49. WHAT CAN I DO FOR THE COMMUNITY?
50. FIRST, DO NO HARM DOn’t BE AN ASSHOLE
51. WHAT IS HELPFUL FOR THE PROJECT?
52. MOST HELPFUL ≠ MOST VISIBLE ≠ MOST glamourous
53. “DEVELOPER EVANGELIST”
54. DOCUMENTATION
55. ON BOARDING
56. TUTORIALS
57. COMMUNITY
58. “MANAGER”
59. FIND YOUr PLACE
60. PAY ATTENTION
61. PASSION
62. MULTIPLy YOUR IMPACT
63. WELCOME TO THE TEAM
64.   @chancancode