| 3 | | 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. |
| 4 | | |
| 5 | | 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]: |
| 6 | | 1. if it's a minor issue, just open a ticket and exit |
| 7 | | 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) |
| 8 | | 1. if it is rejected on the mailing list, exit |
| 9 | | 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 |
| | 3 | '''NB: this page and it's sub-pages are in no way part of Django's official process.''' Feel free to use the wiki as a collaborative whiteboard for reaching agreement on designs of various issues, but please note that all discussion should happen on django-dev. Please read [http://www.djangoproject.com/documentation/contributing/#requesting-features requesting features] for more information on how Django's development process works. |