There is a list of ideas [1] and both improving aggregates and annotations as well as improving error messages are listed there, so I suppose these ideas are still open.
Google doesn't allow you to submit your proposal before March 10, but the submission is only a formality and this doesn't mean you can't work at your proposal. The most important thing is that you should discuss your proposal with Django community before submission, because you will be given many constructive feedback that will help you make your proposal better and improve chances of being accepted. My experience is that it's better to start as early as possible and not to hesitate to publish proposal. AFAIK, there is no problem if there is more than one student working on the same idea. Disclaimer: I'm not a core dev neither GSoC admin, but I was GSoC participant (as a student) last year. [1] https://code.djangoproject.com/wiki/SummerOfCode2014 -- You received this message because you are subscribed to the Google Groups "Django developers" 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/0e3aaa96-0a5f-4948-b9d3-95522b9b1795%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
