Another interesting thing I've found is that packagers really prefer tarballs. They can checksum them. They don't need to download your full history, etc.<p>The tarballs automatically produced by github have names that are annoying and makes things harder for packagers, so I find myself creating "make dist" targets and uploading the result to github. Is there an API for file uploads? (that would be sweet!)<p>I do wish there was a way to provide a format string that would tell github the basename to use for tarballs.<p>If you are jquery and your project is jquery your tarballs look like jquery-jquery-v1.2.3-g654321.tar.gz and the directory basename is the same.<p>If they added the ability to configure it per-repo and used "{{ user }}-{{ repo }}-{{ tag }}-{{ sha1 }}" as the default then they could keep backwards compat and let folks configure it to their liking. It's one of my very few github peeves.
rather more extensive and general, but somewhat related book (Producing Open Source Software): <a href="http://producingoss.com/a" rel="nofollow">http://producingoss.com/a</a>
So like...<p>1. Write Official Documentation (booooring)<p>2. Use Git Flow (version management, boooooring)<p>3. Publish Test Runs (oh, testing.. thats fun right? no...ok...)<p>4. Use GitHub Issues (....)<p>5. Have fun. (yes!!)<p>Ill take one number 5 please. And 1-4 is why Im not a professional programmer.