May I recommend you browse Trac and take a look at the pending tickets regarding aggregation?
This query should give you enough food for thought: http://goo.gl/vvraU It is my understanding that Anssi Kääriäinen is working on an ORM refactor, so speaking to him seems fundamental if you really want to move forward with this, even with the imminent deadline. Some of the tickets you'll find in that query may even have patches, but with the ongoing refactoring it seems as if they're shooting at a moving target. Cheers. AT On Thu, May 2, 2013 at 10:30 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > > On Fri, May 3, 2013 at 4:31 AM, nimesh ghelani <nimeshghel...@gmail.com>wrote: > >> Hey, >> Will like reviews on my proposal >> >> https://gist.github.com/nims11/dbd2f52677377eb60c07 >> >> Hi Nimesh, > > At present, this isn't an especially compelling proposal. > > The bulk of what you're proposing is extremely vague. The #10929 default > NULL issue is well known and understood, but detail on your other proposal > goes no further than "should be simpler". We agree. Now, how are you going > to do that? You haven't given an API proposal, and you're not previously > known to the wider community, so we can't judge whether you have good API > design skills, or whether you've looked at any of the internals to > determine if what you're proposing is technically feasible given the > existing infrastructure. > > On top of that, based on no experience with the query internals, you've > assumed that you'll be able to understand the internals of Django's query > engine, and then design and get consensus on an API plan in a 2 week > window. That's… ambitious. > > Then you've got a 7 week block to implement this plan. This sort of > granularity gives us no confidence that you in any way understand the task > ahead of you. If you can't provide a plan at the granularity of days, or a > week at the *most*, then it's safe to say you haven't actually thought in > detail about the complexity of the problem you're proposing to solve. > > You're proposing a deep dive into the internals of Django's query > infrastructure. Committing to being a mentor for the GSoC is a big > commitment, and there is a limited number of people who are in a position > to mentor you on this project. When combined with the vagueness of what > you're proposing, you haven't exactly inspired the confidence you'll need > to convince someone to commit to mentoring you. > > If you want to be selected for the GSoC, you'll need to provide a lot more > details -- most importantly, evidence that you've thought about the problem > at a level beyond "this looks like a nice problem". > > Yours, > Russ Magee %-) > > -- > 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?hl=en > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
