It's an amazing idea. Thanks for putting it up, Aymeric and Tim! Can we add a question regarding usage of test frameworks (i.e., unittest2, py.test, nose) similar to "Which popular third-party apps do you rely on?" For example "Which test frameworks do you use?" - "unittest2, py.test, nose, other". That would allow us to see if we should / can include features in django.test that may require a specific framework without excluding too many people of our community.
/Markus On Monday, April 27, 2015 at 9:59:24 PM UTC+2, Thorsten Sanders wrote: > > I wrote in that thread too why I dont like such fast releases and at > least someone else asked too to give more options on that one question, on > the developer mailing list its kinda only some people who are writing not > reflecting all the developers such an survey maybe reach more of them and > then the answer about such an important question shouldnt be reduced to 3 > little options a handfull people decided on, that wouldnt reflect what > people really want if they cant choose an real answer. > > Am 27.04.2015 02:46, schrieb Tim Graham: > > The idea of the release schedule question is to form consensus on the > options that have already been proposed in the "1.9 release planning > <https://groups.google.com/d/topic/django-developers/MTvOPDNQXLI/discussion>" > thread. If you have a different idea, please propose it there. > > On Sunday, April 26, 2015 at 6:53:14 AM UTC-4, Thorsten Sanders wrote: >> >> I like the idea of an survey, but find the release question with only 3 >> options quite limited, how about to allow there to put own numbers instead >> of giving fixed answers or at least an other field? >> >> Am 25.04.2015 14:29, schrieb Tim Graham: >> >> Aymeric and I put together a draft: >> >> >> https://docs.google.com/forms/d/1Owv-Y_beohyCm9o2xPamdBnvjreNYoWai3rDloKZxWw/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. >> >> On Wednesday, April 22, 2015 at 4:03:44 AM UTC-4, Federico Capoano wrote: >>> >>> Great idea. >>> The questions look good enough to me. >>> >>> I love django-apps or libraries shipped in python packages. One of the >>> reason I love Django is the fact that it didn't frenetically add stuff to >>> the framework just because it's cool. >>> The good thing of python packages is that you can get some data from >>> pypi (downloads) and github (clones). But we can't do that with contrib >>> apps unfortunately. >>> >>> Federico >>> >>> >>> On Saturday, April 18, 2015 at 1:00:13 AM UTC+2, Tim Graham wrote: >>>> >>>> I had an idea to conduct a survey to get a sense of how developers are >>>> using Django. I first had the idea when the question of maintenance of the >>>> Oracle GIS backend came up. We really have no idea whether or not anyone >>>> is >>>> actually using that backend, and it would be helpful to know so we are not >>>> wasting resources on unused features. Also there's the question of how >>>> often to release Django. I think it would be nice to make that decision >>>> based on some data from the community. >>>> >>>> Is anyone is interested in coordinating such a survey (collating >>>> questions, preparing the online survey, etc.). >>>> >>>> Some question ideas to get started: >>>> >>>> Which database backend(s) do you use? >>>> [ ] Checkbox for each one >>>> >>>> Which contrib apps do you use? >>>> [ ] Checkbox for each one >>>> >>>> How often would you like to see new major version of Django released? >>>> [ ] List some options, probably between 6 and 9 months. >>>> >>>> Describe which version of Django you use (check all the apply): >>>> [ ] I only use long-term support releases. >>>> [ ] I upgrade to the latest stable version as quickly as possible. >>>> [ ] I run off of master. >>>> [ ] I upgrade Django when the version I am using is nearing the end of >>>> its support (or after). >>>> [ ] I don't bother upgrading Django, even if it becomes unsupported. >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com. >> To post to this group, send email to django-d...@googlegroups.com. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/f14071d1-c570-483a-abd2-833e1b47ab4d%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/f14071d1-c570-483a-abd2-833e1b47ab4d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-develop...@googlegroups.com <javascript:>. > To post to this group, send email to django-d...@googlegroups.com > <javascript:>. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/b2c3d0ac-1a8e-4a70-9fb7-24bf6e0e1581%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/b2c3d0ac-1a8e-4a70-9fb7-24bf6e0e1581%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f48c2381-db91-43b3-bb45-e0a4e382d6f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
