Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Communicating in Open Source

Communicating in Open Source

Slides from the Open Source Comes to Campus event at RPI.

Alex Gaynor

April 21, 2012

Transcript

11 slides
  1. WORKFLOW • I have an issue. • Is it an

    issue with the project? • Check Google, StackOverflow, etc. • How do I communicate this to the project? Saturday, April 21, 2012
  2. READ THE FRIENDLY MANUAL • Projects have different preferred communication

    methods. • Your project’s workflow is the only one that matters. • First place to look is the documentation. Saturday, April 21, 2012
  3. WHERE TO ASK FOR HELP • Is there a -dev

    and -users mailing list/IRC channel? • Write in a professional tone. • The shorter, and more self contained the example, the better. • Patience is key. Saturday, April 21, 2012
  4. HOW TO ASK FOR HELP • A clear description of

    your goal, and what you tried. • Steps to reproduce the bug. • Example data if needed. • Your desired output, and the actual output. • Any relevant system info (compiler version, OS, etc.) Saturday, April 21, 2012
  5. ISSUE TRACKERS • Always search first. • Make sure to

    categorize/tag things correctly. • All the steps on how to ask a good question apply to writing a good bug report. • Unit tests! Saturday, April 21, 2012

More Decks by Alex Gaynor

Other Decks in Programming