It seems like everyone's talking about two different things here: 1) Should Django add more apps to contrib? 2) Does staticfiles solve a real need that users of Django have today? Is it the de-facto implementation of a common pattern?
Let's just drop the discussion of the first point for the purposes of this thread. At this point it's clear that contrib isn't going anywhere soon, and certainly not without some concrete proposal by someone and a lot of discussion. So that leaves us with staticfiles, specifically. I've heard countless times from people at conferences, at local meetup groups, and elsewhere who are upset that Django doesn't give them any direction on what to do with their static files. Django is fairly opinionated software, but as soon as you start dealing with static files Django suddenly has no opinion. That's confusing and frustrating for users, to say the least. I think staticfiles is an *excellent* contribution, and if there is some advanced use case that it doesn't do, then let's do our best to make it extensible enough to make that use case possible. Easy things (like bundling media with your app) should be easy, but hard things (like minification and consolidation of js) should be possible. Anyway, that's my 2c. Thanks, Eric Florenzano -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
