= Specifications for various Django features =

This page is meant to be a collaborative whiteboard for reaching agreement on designs of various issues. Usually this information is scattered around Django IRC channel, tickets and mailing lists and is both hard to find and quite often non-conclusive.

Non-trivial design decisions should converge into a clear specification that merges all the bits from different discussion sources. The process should be similar to [http://www.python.org/dev/peps/ PEPs]:
 1. if it's a minor issue, just open a ticket and exit
 1. post your proposal to django-developers mailing list and open a corresponding ticket (review http://www.python.org/dev/peps/pep-0001/#pep-work-flow)
 1. if it is rejected on the mailing list, exit
 1. based on the feedback received, write a specification as a sub-page of this page, link it to the corresponding ticket and announce it to the mailing list

== Specifications ==

Newforms-admin:
 * [wiki:DjangoSpecifications/NfAdmin/MediaAndValidation Media and validation]
 * [wiki:DjangoSpecifications/NfAdmin/FlexibleAppHandling Usability improvements in application handling] (enhancements of the `app` directive)

Fields:
 * Binary field: merge information from #2417 and http://groups.google.com/group/django-developers/browse_thread/thread/266565a23b765ea2

Documentation:
 * [wiki:DjangoSpecifications/Docs/ConvertingRestToOtherFormats Converting the ReST documentation in `doc/` to HTML and PDF]

Core:
 * [wiki:DjangoSpecifications/Core/SingleInstance Single Instance] aka the infamous #17