On Fri, Mar 11, 2011 at 1:14 PM, Simon Litchfield <si...@s29.com.au> wrote: > Who votes we should come up with a django-blessed 'official' default project > layout / directory structure?
Sure -- no disagreement that it would be good to have some common ground with regards to project layout. All we need now is to agree what that blessed project layout should be. :-) And there's the rub. There are a bunch of people with different ideas. For example, take one idea in your list: virtualenv and pip. For many, this won't be even slightly controversial. But for others, it will be a complete show-stopper, because there is many a site that enforces a 'package manager only' approach to system adminstration. So, we have to tread carefully here. At some level, we may just need to make an executive BDFL call. However, a BDFL isn't going to make a call until there is a proposal (or three) on the table. What we need is for someone to drive the discussion and make this happen so that we are in a position to actually bless something. For the record, this isn't a new idea, either. Django's tutorial has said "more coming soon" for as long as I've been involved with Django. At several times over the last couple of years, there have been discussions about adding step 5, 6 and more. One of the ideas that is kicking around is to talk more about project structure, showing how a reusable app fits into the picture; how pip, virtualenv, tools like fabric and chef fit into the picture; and so on. However, writing tutorials takes time, and writing good tutorials takes longer. So -- if you build it, they will come. Someone just needs to build it :-) Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
