Yesterday at PyCon, about a dozen people from the Django core team had a lunch meeting to talk about various ideas we should implement. One idea was to start doing a Django equivalent of Python's PEPs, which would serve as a formal way to document large new features/changes in Django.
The goal would be to have "design documents" in a single place, rather than relying on parsing dozens of micro-decisions made in mailing list threads, Trac tickets, etc. And, importantly, we would only use this for medium-to-large features, so as not to introduce too much inertia. We also talked about doing it immediately, just using pull requests on GitHub, to get some momentum going. No need to build any fancy systems, etc. Today at the sprints, I went ahead and started drafting how this would work. Here is a new GitHub repo for DEPs (Django Enhancement Proposals): https://github.com/django/deps And here is DEP 1, a draft attempt to document how the process works: https://github.com/django/deps/blob/master/deps/0001.txt Note the "TODO: Next steps" at the bottom. I'm not exactly sure what the best process would be once a DEP is formally created. Can somebody with more familiarity with Python's PEP process provide some suggestions? Adrian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CABm4ZCT1S1_ybYVe_0BGKvGAsQx3VDsD0KWZtBfR9fD6nOU7vQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
