Hi,
On Saturday 25 April 2015 15:29:30 Tim Graham wrote:
> Aymeric and I put together a draft:
>
> https://docs.google.com/forms/d/1Owv-Y_beohyCm9o2xPamdBnvjreNYoWai3rDloKZxW
> w/viewform
>
> All questions are optional so you can just click through it to view the
> questions. We'll probably clear any responses before its finalized anyway.
>
> Let us know if you think we should make any additions or changes.
>
This looks great, thanks for putting it together. There are only a few things
I'd like to add.
First of all, a question I find interesting about the general use pattern: "Do
you use Django mainly for one big project, or many small ones?" I'm not sure
what's the best way to phrase it, but I think it may be important for
interpreting other answers (e.g. larger projects will probably tend to move
slower w.r.t releases, will tend to use more contrib and 3rd-party apps, etc).
In "components": Request processing (URLs, middleware, view decorators).
Also, while not a "component" per se, Django's documentation is often cited as
a valuable resource, and a lot of effort goes into it; I'm not sure adding it
as a component adds value, but perhaps we should ask about topic guides vs.
reference or something of the sort.
In the question about "contrib" apps, should we include the removed apps
(comments, markup, formtools, localflavor)?
In the list of 3rd-party backends: I'm not sure what are the criteria for
being in this list; two other 3rd-patyr backends I'm aware of are django-
pyodbc-azure (which I've used) and the proprietary mxODBC-django.
Again, thanks for the initiative,
Shai.
