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.
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!
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)
"Dad, if you dont get it, its because I didnt do it."
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).
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
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.