DjangoCon 2008 Keynote Questions: State of Django
summary
Thanks to contributors; Rails-style instant-feedback influenced the project. Marty's file storage abstraction exists and can be split out but core team likely won’t maintain standalone forks. CI is flaky because of a buildbot test race in file-storage tests; Buildbot expertise is needed. Core is drafting a semi-formal policy for what becomes django.contrib and prefers to wait before endorsing one of 3–5 schema migration tools so innovation isn’t cut off. Low-level multiple database plumbing is in place but not yet public or documented.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:55What frameworks have influenced Django
- 1:55What is the future of Django
- 2:35Django deutils
- 3:35Django is easy to use
- 4:55Django projectcom
- 5:55Community focus
- 7:00Django contribs
- 9:10Reusable Applications
- 10:35Multiple Databases
related talks
29mHow Django helped us make a better conference website
26mDjango Unstrained
33mThe D is Silent: Challenges in Teaching Django
23mFiles in Django
28mMaking a Splash with your Open Source Project
38mdjango-cms: Friends don't let friends use Drupal.
23mStanding on the Shoulders of Giants: The Kotti Web Application Framework
53mLightning Talks and Closing