No one likes an unkempt public area - Open Source guidelines to Cleanliness

&#62; You have an obligation to release code that is tested. Automated spec is preferrable. You have an obligation to document your code and build process, most especially — your contribution and pull request policy<p>No I don't. Unless I signed a document saying otherwise you should consider yourself damn lucky that you get to access my source code.

Open source developers tend to fall into two camps:<p>1. I am providing a public service, so I'll do my best to make it simple, complete, accessible, and reliable.<p>2. I've invested a lot of my precious time writing this code and am graciously providing it free of charge. Therefore, you should consider yourself lucky that I'm allowing you to use it at all.<p>In my experience, it's difficult for those in one camp to find common ground with the other. Group 2 tends to flourish in wild frontiers, whereas those in group 1 tend to do better in more established areas.

I think this is a bit uppity.<p>Many people are graciously letting people share in stuff that they themselves need to have. It's laughable to obligate the guy throwing the free picnic or donating his used couch to anything and similarly so for given code.