The document discusses committing to open source projects by joining a community to avoid working alone. It recommends finding a project that scratches a personal itch, using the right tools for the job, and looking out for potential blockers. The goal is to provide examples of how to successfully contribute to open source.

1. Commit yourself already:
Contributing to open source
Donnie Berkholz, Ph.D.
Research Director — Development, DevOps & IT Ops
PyMNtos (Twin Cities Python user group), Apr 2016

2. 2

3. Every open-source project is always understaffed.
3

4. Motivations are key – Scratch an itch
Wing-Chi Poon, CC BY-SA
4

5. 5
Public domain
Finding and joining your community

6. 6
Going it yourself is a long, lonely road
Donnie Berkholz Source: http://redmonk.com/dberkholz/2013/04/22/the-size-of-open-source-communities-and-its-impact-upon-activity-licensing-and-hosting/

7. 7
Bisor Todorov, CC BY
Use the right (not always best) tools for the job

8. 8
Jimmy Guano, CC BY
Find and use the right on-ramps

9. 9
J.P. Lon, CC BY-SA
Blockers – what to look out for

10. Time for some
examples
10

11. Donnie Berkholz
Twitter: @dberkholz
donnie.berkholz@451research.com
11
Open source is all about community.
MINNEAPOLIS

12. Some images from this presentation
are Creative-Commons licensed.
https://creativecommons.org/licenses/by-sa/3.0/
https://creativecommons.org/licenses/by/3.0/
12