Triaging Rails Issues

A lighting talk on Triaging Rails issues by Nick Cox. Given at Crystal Commerce for the Seattle Rails Meetup on 04/16/13.

Transcript

1. Triaging Rails Issues Nick Cox Saturday, May 11, 13
2. ABOUT ME • Rails Developer at Navigating Cancer • Open Source Maven • Taco Aficionado thenickcox @everydaytype Saturday, May 11, 13
3. *As of April 1, 2013 473 7ish 7ish open issues issues filed/day issues closed/day core team 40 Saturday, May 11, 13
4. triage |trēˈäZH, ˈtrēˌäZH| n. the process of determining the most important people or things from amongst a large number that require attention. Saturday, May 11, 13
5. http://www.flickr.com/photos/starheadboy/7416290638 DON’T BE A HERO. Saturday, May 11, 13
6. TRIAGING 1-2-3 ONE Bug? Try to reproduce it. TWO Pull request? Comment. THREE There is no step 3. Saturday, May 11, 13
7. BENEFITS TRIAGING of •Become a better developer. •Triaging can lead to commits. Commits can lead to glory. •Sense of community and ownership. Saturday, May 11, 13
8. The right tool for the job: codetriage.com Saturday, May 11, 13
9. Subscribe to a project, receive emails. Saturday, May 11, 13
10. TIPS FOR GOOD TRIAGING http://www.flickr.com/photos/lakatosdaniel/8625848668/ Saturday, May 11, 13
11. ADD TO THE CONVERSATION. http://www.flickr.com/photos/silvertrace/1394642335/ Saturday, May 11, 13
12. BE KIND. http://www.flickr.com/photos/gunnisal/2340547359/ Saturday, May 11, 13
13. REPORT BACK. http://www.flickr.com/photos/chrisgold/3255234042/ Saturday, May 11, 13
14. thank you. thenickcox @everydaytype Saturday, May 11, 13