1. Andy Lester @petdance Projects,Communityand Github
2. Who is Github for?
4. Github is notfor end users.
5. Whoo! Exposure!Nat has 171,000 readers at radar.oreilly.com
6. Somebody clicks the link and wants to download it, and what theyre presented with is a dev-oriented home page.
7. The download link isnt very descriptive.
8. Github is for those who like tobuild from source.
9. Your usersprobably dont.
10. To the newcomer, the source tree is unimportant.
11. Whats it do?Whats it look like?Do I want to use it?
12. Make a project site.• Answer the newcomers questions.• Aimed toward the end users.• Users who are not as ninja as you.• Make download + install incredibly obvious.
13. Make a project site.
14. Make a project site.
15. Get your own domain.• Not tied to github, in case things change.• $10/year = dirt-cheap investment• Which is easier to remember? • http://github.com/petdance/ack • http://betterthangrep.com/
16. Visible, documented releases matter!
17. Releases matter!
18. Release for simplicity• Releases are an afﬁrmation: "Yes, you can use this."• Single, veriﬁable tarball.• Nobody wants to run autoconf.• Users expect them.
19. Release for history and visibility• Lets others build on your work.• Make a milestone with history.• Maintain an accurate, human-written changelog of all releases. • A dump of commit messages is not a changelog!
20. Optimize for your users sake, not your own.
21. The needs of the manyoutweigh the needs of the few, or the one.
22. About me
23. About @petdance• Perl guy: ack, prove, WWW::Mechanize• Programming for money since the 1980s• I sling PHP for B2B web apps for a (eww!) midsize corporation.• From the midwest, Chicago area• Diversity = good (c.f. @ginatrapani yesterday)
24. "Dad, if you dont get it, its because I didnt do it."
25. Github projects have a low barrier to entry.
26. The good part:Anyone can do it.
27. The bad part:Anyone can do it.
28. Newbies expect theirchanges to be accepted.
29. "Cant you just...?"
30. Be gentle in your rejections. Brevity may beperceived as harsh.
31. That box is too small.
32. You want to acceptchanges from newbies if at all possible.
33. Dont reject patches just because of...• No tests• No documentation• Not following code standards• Those can all be ﬁxed!
34. In this mornings mail...
35. I am happy to suggest use cases that Ihave found useful. What is the best way -to mailing list, on a wiki somewhere,email to you.Dont quite feel up to being moreproactive. I am dyslexic and find writingstuff hard (and finishing of writing etc).
36. Make a project guide• Small chunks of the elephant • "TODO: Better error handling" is not helpful to the newbie.• Project direction• Coding standards• Workﬂow + branch strategy
37. Monitor your network
38. Thank you• Put yourself in the newbies shoes.• Make a project home page outside Github.• Visible, documented releases matter.• Optimize for others, not yourself.• Use Github to encourage your community, not fend it off.• Thank you for listening and for Githubbing.