| 3 | | Drafting, so using Pirate Pad for now: |
| 4 | | http://piratepad.net/9w7ILjRkH2 |
| | 3 | See also [http://code.djangoproject.com/wiki/CaseStudyLeads leads for case studies]. |
| | 4 | |
| | 5 | == Demographics == |
| | 6 | |
| | 7 | What size is your company, and what size is the team that adopted Django? |
| | 8 | |
| | 9 | Was your adoption for a greenfield project, or did you migrate an existing project? |
| | 10 | |
| | 11 | If migrating, what was the codebase in before, and what size was the code before and after? |
| | 12 | |
| | 13 | How large was your first Django project? Was it deliberately experimental? |
| | 14 | |
| | 15 | How much effort was spent adopting Django? How much did it cost or save? |
| | 16 | |
| | 17 | == Adoption == |
| | 18 | |
| | 19 | How did you begin considering Django? |
| | 20 | |
| | 21 | Who was the champion / change initiator? |
| | 22 | |
| | 23 | When debating adoption, what concerns were raised? Have these concerns proved to be valid? |
| | 24 | |
| | 25 | What arguments, support, or materials helped win the debate whether to adopt Django? |
| | 26 | |
| | 27 | Was there internal organizational stress in adoption? If so, what might have improved the situation? |
| | 28 | |
| | 29 | == Maturity == |
| | 30 | |
| | 31 | Did you train your existing team to use Django, or did they learn it on their own? |
| | 32 | |
| | 33 | Have you found hiring for Django easier or more difficult than the prior skill sets? |
| | 34 | |
| | 35 | What do you consider to be key successes in your adoption of Django? |
| | 36 | |
| | 37 | What shortcomings have you encountered during your adoption? |
| | 38 | |
| | 39 | What do you consider to be the best and worst things about Django? |
| | 40 | |
| | 41 | How many unique users, pageviews per month? |
| | 42 | What request latency do you see? How many requests per second per web server? |
| | 43 | |
| | 44 | What tooling do you use around deployment, source control, etc? |
| | 45 | |
| | 46 | What development methodology do you use? |
| | 47 | |
| | 48 | Do you plan to expand or retract your use of Django? |
| | 49 | |
| | 50 | Would you be willing to make a credited testimonial about Django? Both technical and business soundbites are useful. |
| | 51 | |
| | 52 | == Community feedback == |
| | 53 | |
| | 54 | Did you find the following useful: |
| | 55 | |
| | 56 | * documentation |
| | 57 | * django-* mailing lists |
| | 58 | * IRC |
| | 59 | * Conferences |
| | 60 | * Private training |
| | 61 | * Public training |
| | 62 | |
| | 63 | If you could change one thing about Django, what would it be? |
| | 64 | |
| | 65 | == Community membership == |
| | 66 | |
| | 67 | Have you contributed any patches to Django? |
| | 68 | * How happy were you with that experience? |
| | 69 | |
| | 70 | Do you maintain any customizations of Django (cache backends, template tags, etc.)? |
| | 71 | |
| | 72 | Do you maintain any private patches of the Django codebase? |
| | 73 | * How happy were you with that experience? |
| | 74 | |
| | 75 | Would you consider hosting a sprint in support of Django? (Support for organizing is readily available.) |
| | 76 | |
| | 77 | What third party Django packages/projects did you use? |
| | 78 | * How happy were you with that experience? |
| | 79 | |
| | 80 | What open source projects came out of your effort? |
| | 81 | * Who else is using your open source efforts? |
| | 82 | * Have you had any major contributions to your open source projects from resources outside of your organization? |