Django Package Thunderdome: Is your package worthy?
+Presented by Audrey Roy & Daniel Greenfeld
+ * Name should tell you what it does.
+ * Real need and be useful.
+ * Small, narrow focus is better.
+ * No docs means the package is pre-alpha
+ * Doc strings != documentation
+ * If there are dependencies, they should be in the docs
+ * Installation should be bulletproof
+ * Tests improve reliability
+ * Tests make it easy to advance python/django versions
+ * Tests make it easier for community submissions
+ * When was the last commit?
+ * How frequent are the commits?
+ * Are there periodic version updates?
+ * How many contributors?
+ * Proper attribution of authors?
+ * Installation should be minimally invasive
+ * Do not confuse modularity with over-engineering
+ 8. Availability on PyPI
+ * Latest release on PyPI
+ * Should not have to go to repo for working version
+ * Proper version numbers
+ * Great: Github/Bitbucket
+ * OK: Launchpad/SourceForge
+ * Outdated: Google project hosting
+ * Companies prefer BSD or MIT
+ * http://opensource.org/licenses/category