29 ways to get started in open source

Slide 1

Slide 1 text

29 ways to get started in open source Andy Lester, http://petdance.com/ Wednesday, June 13, 12

Slide 2

Slide 2 text

Wednesday, June 13, 12

Slide 3

Slide 3 text

Rule 1 Wednesday, June 13, 12

Slide 4

Slide 4 text

You are worthy Wednesday, June 13, 12

Slide 5

Slide 5 text

What’s a good project to help out with? Wednesday, June 13, 12

Slide 6

Slide 6 text

Best project to help on: one you use. Wednesday, June 13, 12

Slide 7

Slide 7 text

2nd best: one you want to use. Wednesday, June 13, 12

Slide 8

Slide 8 text

Listen & learn Wednesday, June 13, 12

Slide 9

Slide 9 text

Listen & learn • How does project work ﬂow? • Who are leaders? Dictator or committee? • What’s being worked on? • What does the project value? Wednesday, June 13, 12

Slide 10

Slide 10 text

Listen & learn • Join a mailing list. • Read blogs of leaders. • Join IRC channel. • Attend a user group meeting. Wednesday, June 13, 12

Slide 11

Slide 11 text

Every project is different. Wednesday, June 13, 12

Slide 12

Slide 12 text

Wednesday, June 13, 12

Slide 13

Slide 13 text

Bug management Wednesday, June 13, 12

Slide 14

Slide 14 text

Report a bug. Wednesday, June 13, 12

Slide 15

Slide 15 text

Enhance a bug report. Wednesday, June 13, 12

Slide 16

Slide 16 text

A bug ticket is not a static document! Wednesday, June 13, 12

Slide 17

Slide 17 text

Enhance a bug report. • “I recreated this on Ubuntu with the 1.6 release per the ticket. On Mac OS X, it also failed, but with a different error message and with a stack trace.” • (And give the message and contents of the stack trace!) Wednesday, June 13, 12

Slide 18

Slide 18 text

Isolate a bug. Wednesday, June 13, 12

Slide 19

Slide 19 text

Isolate a bug. • “I was not able to recreate this under Firefox 11.0, but it does happen on Firefox 9.1 and Safari 2.4.” • If you have a theory, provide it. • “I remember reading that Firefox 11 was more forgiving in handling JavaScript that does X.” Wednesday, June 13, 12

Slide 20

Slide 20 text

Isolate a bug. • Be careful you are clear what is theory and guessing, and what is fact you’ve proven. • Avoid sweeping guesses. • Bad: “This happens with every template.” • Good: “I tried this on these seven templates: A, B, C, M, N, P and X”. Wednesday, June 13, 12

Slide 21

Slide 21 text

Write a test Wednesday, June 13, 12

Slide 22

Slide 22 text

Silence a compiler warning. Wednesday, June 13, 12

Slide 23

Slide 23 text

Close a ticket Wednesday, June 13, 12

Slide 24

Slide 24 text

Document an API: Examples! Wednesday, June 13, 12

Slide 25

Slide 25 text

Document a process Wednesday, June 13, 12

Slide 26

Slide 26 text

Fix the website Wednesday, June 13, 12

Slide 27

Slide 27 text

Translate something. Wednesday, June 13, 12

Slide 28

Slide 28 text

Tweet some news Wednesday, June 13, 12

Slide 29

Slide 29 text

Write a blog post Wednesday, June 13, 12

Slide 30

Slide 30 text

How did you use the project? Wednesday, June 13, 12

Slide 31

Slide 31 text

What worked? What didn’t? Wednesday, June 13, 12

Slide 32

Slide 32 text

Wednesday, June 13, 12

Slide 33

Slide 33 text

Go to a user group meeting Wednesday, June 13, 12

Slide 34

Slide 34 text

Test a beta or RC Wednesday, June 13, 12

Slide 35

Slide 35 text

Answer a question Wednesday, June 13, 12

Slide 36

Slide 36 text

Draw a logo Wednesday, June 13, 12

Slide 37

Slide 37 text

Welcome a newcomer Wednesday, June 13, 12

Slide 38

Slide 38 text

Talk at a user group Wednesday, June 13, 12

Slide 39

Slide 39 text

Do what needs to get done Wednesday, June 13, 12

Slide 40

Slide 40 text

Thank someone. Wednesday, June 13, 12

Slide 41

Slide 41 text

Thank you for listening. http://speakerdeck.com/u/petdance/ Wednesday, June 13, 12