Release for simplicity
• Releases are an afﬁrmation: "Yes, you can
• Single, veriﬁable tarball.
• Nobody wants to run autoconf.
• Users expect them.
Release for history
• 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
• Perl guy: ack, prove, WWW::Mechanize
• Programming for money since the 1980s
• I sling PHP for B2B web apps for a
• From the midwest, Chicago area
• Diversity = good
(c.f. @ginatrapani yesterday)
"Dad, if you don't get it, it's because I didn't do it."
I am happy to suggest use cases that I
have found useful. What is the best way -
to mailing list, on a wiki somewhere,
email to you.
Don't quite feel up to being more
proactive. I am dyslexic and find writing
stuff 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
• Put yourself in the newbie's 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