Guidelines for writing, distributing and using Django applications

See

• ​http://groups.google.com/group/django-developers/browse_thread/thread/bdcad26ab044cb96
• ​http://www.b-list.org/weblog/2008/sep/07/slides/ and ​http://media.b-list.org/presentations/2008/djangocon/reusable_apps.pdf

Guidelines for reusable application authors

• namespace: apps should live in django.apps, i.e. if your app is named frobnicate, your code should be in django.apps.frobnicate
  • FIXME alternative: require use of namespace packages, see ​http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages , review how Zope does it
• FIXME Django version: somehow the Django version used has to be conveyed (django1.0-comments?), again Zope app versioning should help
• publishing: apps should be packaged with setuptools and published in the ​Python Package Index, under trove category Framework :: Django
• dependencies: ordinary setuptools dependency handling

Package index

Additionally to ​PyPI (the Python Package Index), a separate indexing service with ratings, groupings and whatnot would be useful.

• ​Django Pluggables is a nice start
• see ReusableAppResources for links to other collections of re-usable apps