Re: structural & functional review of django documentation

2016-01-01 Thread Doug Epling
Hey Tim -- Basically, we need data. My recommendation involves two separate initiatives. First is, has been, a discussion open for spectators but limited participants to core members. Asside from its subject pertaining current state and future path, all other details are above my pay grade.

Re: structural & functional review of django documentation

2016-01-01 Thread Tim Graham
There weren't any secret discussions among the core team about the data from the survey. It helped to inform the roadmap as far as how often a Django release should happen, where 6 and 12 months were the most popular answers, and we decided on 8 months as a compromise between the two (all of th

Re: structural & functional review of django documentation

2016-01-01 Thread Doug Epling
I know some might have hoped I would just go away. But generally speaking when I say I will do something I follow through. At the very least I can work on the Glossary. I looked at the poll of developers from last May. I loaded the results in an R data.frame, but I did not f

Re: delegating our static file serving

2016-01-01 Thread Aymeric Augustin
Hello Collin, > On 31 déc. 2015, at 23:44, Collin Anderson wrote: > > I feel like the insecure flag could get renamed to inefficient or something > like that. This view is insecure for serving user-uploaded files, for reasons Florian hinted at. Browsers “helpfully” get a lot things wrong for

Re: delegating our static file serving

2016-01-01 Thread Curtis Maloney
On 01/01/16 15:49, Fabio Caritas Barrionuevo da Luz wrote: A question: are there any plans to also improve MEDIA files (user uploaded files) in any foreseeable future? Perhaps this is outside the scope of Django, but I believe Django could provide by default, any option to get a little more cont