Re: [GSoC'14] Proposal: Improve annotation and aggregation
As far as I am aware already the tasks that are listed out in the GSoC idea page have been completed by someone and there is a PR for that purpose also. https://github.com/django/django/pull/2184 -- 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/f8af5899-b48a-4156-96c1-ba96b12b909b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [GSoC'14] Proposal: Improve annotation and aggregation
Thank you for your reply. I'll try my best :) Regards, Shamim On Thursday, March 20, 2014 3:30:44 PM UTC+6, Russell Keith-Magee wrote: > > > On Thu, Mar 20, 2014 at 5:27 PM, Russell Keith-Magee < > rus...@keith-magee.com > wrote: > >> >> On Thu, Mar 20, 2014 at 5:21 PM, Shamim Hasnath >> <sha...@hasnath.net >> > wrote: >> >>> Hello, >>> I'm Shamim Hasnath, 3rd year student, studying CSE in Bangladesh >>> University of Engineering & Technology (BUET), Dhaka, Bangladesh. Besides >>> my studies I worked for over a year as a part time Django developer in a >>> software company located in Dhaka, Bangladesh. I developed several Django & >>> GAE apps there. >>> >>> Here's my blog articles on django: >>> http://www.hasnath.net/blog/category/django >>> >>> I'd like to work on *Improve annotation and aggregation. *I'm familiar >>> with MySQL, Oracle, PostgreSQL and SQLite databases. I've checked all the >>> tickets regarding this. >>> >>> I have always wanted to contribute to Django project. GSoC would be a >>> great opportunity for me. >>> >> >> Hi Shamim, >> >> If you want to participate in the GSoC with Django, you'll need to write >> a project proposal. This is a *lot* more work than saying "I'd like to work >> on annotation". Here's a link to an example proposal from last year that >> was successful: >> >> https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 >> > > My apologies - I accidentally hit send mid reply. > > You've got until Friday to get this proposal written and submitted to > Google, so if you're expecting to get feedback from the community and > integrate that feedback into your proposal, you're going to need to get > writing. Getting your proposal reviewed by the community isn't mandatory, > but all the successful proposals in past years have been through at least > one community review - I'd be very surprised if you can write an acceptable > proposal on your first attempt. > > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/cadefd53-d06c-4536-bc44-fc3bf8b3965f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [GSoC'14] Proposal: Improve annotation and aggregation
On Thu, Mar 20, 2014 at 5:27 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > > On Thu, Mar 20, 2014 at 5:21 PM, Shamim Hasnath <sha...@hasnath.net>wrote: > >> Hello, >> I'm Shamim Hasnath, 3rd year student, studying CSE in Bangladesh >> University of Engineering & Technology (BUET), Dhaka, Bangladesh. Besides >> my studies I worked for over a year as a part time Django developer in a >> software company located in Dhaka, Bangladesh. I developed several Django & >> GAE apps there. >> >> Here's my blog articles on django: >> http://www.hasnath.net/blog/category/django >> >> I'd like to work on *Improve annotation and aggregation. *I'm familiar >> with MySQL, Oracle, PostgreSQL and SQLite databases. I've checked all the >> tickets regarding this. >> >> I have always wanted to contribute to Django project. GSoC would be a >> great opportunity for me. >> > > Hi Shamim, > > If you want to participate in the GSoC with Django, you'll need to write a > project proposal. This is a *lot* more work than saying "I'd like to work > on annotation". Here's a link to an example proposal from last year that > was successful: > > https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 > My apologies - I accidentally hit send mid reply. You've got until Friday to get this proposal written and submitted to Google, so if you're expecting to get feedback from the community and integrate that feedback into your proposal, you're going to need to get writing. Getting your proposal reviewed by the community isn't mandatory, but all the successful proposals in past years have been through at least one community review - I'd be very surprised if you can write an acceptable proposal on your first attempt. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84-oZLo7KCjEGRTZAyDouLKfhymtecfKLNANRMozrHZd4Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [GSoC'14] Proposal: Improve annotation and aggregation
On Thu, Mar 20, 2014 at 5:21 PM, Shamim Hasnath <sha...@hasnath.net> wrote: > Hello, > I'm Shamim Hasnath, 3rd year student, studying CSE in Bangladesh > University of Engineering & Technology (BUET), Dhaka, Bangladesh. Besides > my studies I worked for over a year as a part time Django developer in a > software company located in Dhaka, Bangladesh. I developed several Django & > GAE apps there. > > Here's my blog articles on django: > http://www.hasnath.net/blog/category/django > > I'd like to work on *Improve annotation and aggregation. *I'm familiar > with MySQL, Oracle, PostgreSQL and SQLite databases. I've checked all the > tickets regarding this. > > I have always wanted to contribute to Django project. GSoC would be a > great opportunity for me. > Hi Shamim, If you want to participate in the GSoC with Django, you'll need to write a project proposal. This is a *lot* more work than saying "I'd like to work on annotation". Here's a link to an example proposal from last year that was successful: https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 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/CAJxq849Lm0okaanf4rHRVkaqkk7Cmweszvx1ghT3fqauL8BP%3DQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[GSoC'14] Proposal: Improve annotation and aggregation
Hello, I'm Shamim Hasnath, 3rd year student, studying CSE in Bangladesh University of Engineering & Technology (BUET), Dhaka, Bangladesh. Besides my studies I worked for over a year as a part time Django developer in a software company located in Dhaka, Bangladesh. I developed several Django & GAE apps there. Here's my blog articles on django: http://www.hasnath.net/blog/category/django I'd like to work on *Improve annotation and aggregation. *I'm familiar with MySQL, Oracle, PostgreSQL and SQLite databases. I've checked all the tickets regarding this. I have always wanted to contribute to Django project. GSoC would be a great opportunity for me. Thank you. Regards, Shamim http://hasnath.net http://github.com/sha256 http://bitbucket.org/sha256 http://pypi.python.org/pypi/var_dump -- 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/968e42df-30b5-4453-b774-57110ab731e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Improve annotation and aggregation
Hey, Sagar, I just wanted to say thank you in advance for tackling Annotation/Aggregation. IIRC, Anssi Kääriäinen was working on a large ORM refactor which put his improvements to aggregation on hold. It would be worth checking out if he has moved forward, and I'm sure he will have more than a few pointers to give you in this subject. Off the top of my head, two tickets worth checking out are #11305 and #14030, which are somewhat related and much needed by the community (me included), based on what I saw in the comments. I've even helped bring the patch to #11305 up to date twice, but it hasn't been merged pending said refactoring and/or a solution to #14030. https://code.djangoproject.com/ticket/11305 https://code.djangoproject.com/ticket/14030 Good luck and happy coding! Cheers, AT On Tue, Dec 10, 2013 at 7:27 AM, Sagar Ghuge <ghuge...@gmail.com> wrote: > Thanks for Guidelines...I am aware about the GSoC 2014 timeline. That's > why I am starting my work upon this as early as I can do. As you mentioned > , I will try to tackle tickets and once I am familiar with the Django I > will propose the project. :) > > > On Tuesday, December 10, 2013 4:47:17 AM UTC+5:30, Russell Keith-Magee > wrote: > >> >> On Mon, Dec 9, 2013 at 8:59 PM, Sagar Ghuge <ghug...@gmail.com> wrote: >> >>> Hi, >>> >>> I am planning to participate in GSOC 2014 and i would like to contribute >>> in Django as it is working on my area of interest that is Python. Is >>> anybody working on this project. Or can any one mentor me or Guide me >>> through this. I forgot to mention that I am totally new to this as I have >>> an overview about the what Django is and all. Thanks. >>> >> >> Hi Sagar, >> >> You're a little early -- we haven't even begun to think about GSoC 2014 >> yet! However, if you have an interest in annotation and aggregation, that's >> an area that could be a candidate for a GSoC project. >> >> However, you're going to need to do two things: >> >> 1) Make a specific proposal. "Improve annotation and aggregation" is a >> title, not a proposal. A GSoC proposal is a multi-page document, containing >> detailed design plans, and a timetable on which we can evaluate your >> progress. >> >> 2) Demonstrate that you know what you are doing. The annotation and >> aggregation tools in Django are a complex part of the ORM framework. >> Volunteering to mentor a GSoC student is a time consuming activity, so >> mentors want to be sure that their time will be well spent. If you are >> proposing a simple project, you would just need to demonstrate that you can >> code. However, if you're proposing to dive deep into the ORM, you're going >> to need to prove that you know what you're doing. This means developing a >> reputation for working on hard problems in the ORM. >> >> In short, we're not going to approve a project unless we know what we're >> going to get at the end, and we have confidence that you are capable of >> delivering that product. >> >> The good news is that you have several months to do both of these things. >> GSoC 2014 won't open until March/April, so you have three months in which >> you can work on smaller existing tickets to establish your credentials, and >> develop a plan for what you want to tackle in the GSoC. Take that time to >> get familiar with the Django codebase, and take a look at some existing >> tickets against the ORM [1]. See if you can develop fixes for some of those >> tickets - especially if there are any tickets related to aggregation. >> >> Once you've done a few tickets, start working on a draft for your GSoC >> proposal. Look in the Django-develoeprs archives for examples of past >> successful proposals, and try your hand at a draft of your own proposal. >> Send that draft to django-developers, indicating that you're looking for >> feedback. If you start on this drafting process early, the chance of your >> proposal being picked up is much higher, because you'll get much more >> feedback than someone who submits a proposal on the last day and gets no >> feedback. >> >> I hope I haven't scared you off! Best of luck with your GSoC aspirations! >> >> [1] https://code.djangoproject.com/query?status=assigned=new; >> component=Database+layer+(models%2C+ORM) >> >> 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.
Re: Improve annotation and aggregation
Thanks for Guidelines...I am aware about the GSoC 2014 timeline. That's why I am starting my work upon this as early as I can do. As you mentioned , I will try to tackle tickets and once I am familiar with the Django I will propose the project. :) On Tuesday, December 10, 2013 4:47:17 AM UTC+5:30, Russell Keith-Magee wrote: > > > On Mon, Dec 9, 2013 at 8:59 PM, Sagar Ghuge <ghug...@gmail.com > > wrote: > >> Hi, >> >> I am planning to participate in GSOC 2014 and i would like to contribute >> in Django as it is working on my area of interest that is Python. Is >> anybody working on this project. Or can any one mentor me or Guide me >> through this. I forgot to mention that I am totally new to this as I have >> an overview about the what Django is and all. Thanks. >> > > Hi Sagar, > > You're a little early -- we haven't even begun to think about GSoC 2014 > yet! However, if you have an interest in annotation and aggregation, that's > an area that could be a candidate for a GSoC project. > > However, you're going to need to do two things: > > 1) Make a specific proposal. "Improve annotation and aggregation" is a > title, not a proposal. A GSoC proposal is a multi-page document, containing > detailed design plans, and a timetable on which we can evaluate your > progress. > > 2) Demonstrate that you know what you are doing. The annotation and > aggregation tools in Django are a complex part of the ORM framework. > Volunteering to mentor a GSoC student is a time consuming activity, so > mentors want to be sure that their time will be well spent. If you are > proposing a simple project, you would just need to demonstrate that you can > code. However, if you're proposing to dive deep into the ORM, you're going > to need to prove that you know what you're doing. This means developing a > reputation for working on hard problems in the ORM. > > In short, we're not going to approve a project unless we know what we're > going to get at the end, and we have confidence that you are capable of > delivering that product. > > The good news is that you have several months to do both of these things. > GSoC 2014 won't open until March/April, so you have three months in which > you can work on smaller existing tickets to establish your credentials, and > develop a plan for what you want to tackle in the GSoC. Take that time to > get familiar with the Django codebase, and take a look at some existing > tickets against the ORM [1]. See if you can develop fixes for some of those > tickets - especially if there are any tickets related to aggregation. > > Once you've done a few tickets, start working on a draft for your GSoC > proposal. Look in the Django-develoeprs archives for examples of past > successful proposals, and try your hand at a draft of your own proposal. > Send that draft to django-developers, indicating that you're looking for > feedback. If you start on this drafting process early, the chance of your > proposal being picked up is much higher, because you'll get much more > feedback than someone who submits a proposal on the last day and gets no > feedback. > > I hope I haven't scared you off! Best of luck with your GSoC aspirations! > > [1] > https://code.djangoproject.com/query?status=assigned=new=Database+layer+(models%2C+ORM) > > > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/03ee95a1-3964-40be-a7ee-f97a19ce1b0e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Improve annotation and aggregation
On Mon, Dec 9, 2013 at 8:59 PM, Sagar Ghuge <ghuge...@gmail.com> wrote: > Hi, > > I am planning to participate in GSOC 2014 and i would like to contribute > in Django as it is working on my area of interest that is Python. Is > anybody working on this project. Or can any one mentor me or Guide me > through this. I forgot to mention that I am totally new to this as I have > an overview about the what Django is and all. Thanks. > Hi Sagar, You're a little early -- we haven't even begun to think about GSoC 2014 yet! However, if you have an interest in annotation and aggregation, that's an area that could be a candidate for a GSoC project. However, you're going to need to do two things: 1) Make a specific proposal. "Improve annotation and aggregation" is a title, not a proposal. A GSoC proposal is a multi-page document, containing detailed design plans, and a timetable on which we can evaluate your progress. 2) Demonstrate that you know what you are doing. The annotation and aggregation tools in Django are a complex part of the ORM framework. Volunteering to mentor a GSoC student is a time consuming activity, so mentors want to be sure that their time will be well spent. If you are proposing a simple project, you would just need to demonstrate that you can code. However, if you're proposing to dive deep into the ORM, you're going to need to prove that you know what you're doing. This means developing a reputation for working on hard problems in the ORM. In short, we're not going to approve a project unless we know what we're going to get at the end, and we have confidence that you are capable of delivering that product. The good news is that you have several months to do both of these things. GSoC 2014 won't open until March/April, so you have three months in which you can work on smaller existing tickets to establish your credentials, and develop a plan for what you want to tackle in the GSoC. Take that time to get familiar with the Django codebase, and take a look at some existing tickets against the ORM [1]. See if you can develop fixes for some of those tickets - especially if there are any tickets related to aggregation. Once you've done a few tickets, start working on a draft for your GSoC proposal. Look in the Django-develoeprs archives for examples of past successful proposals, and try your hand at a draft of your own proposal. Send that draft to django-developers, indicating that you're looking for feedback. If you start on this drafting process early, the chance of your proposal being picked up is much higher, because you'll get much more feedback than someone who submits a proposal on the last day and gets no feedback. I hope I haven't scared you off! Best of luck with your GSoC aspirations! [1] https://code.djangoproject.com/query?status=assigned=new=Database+layer+(models%2C+ORM) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq849GkzAv8F7SP0axf_Dbf8hhwU_gzYdoBCi%3D%3DHcULP3NCQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Improve annotation and aggregation
Hi, I am planning to participate in GSOC 2014 and i would like to contribute in Django as it is working on my area of interest that is Python. Is anybody working on this project. Or can any one mentor me or Guide me through this. I forgot to mention that I am totally new to this as I have an overview about the what Django is and all. Thanks. -- 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/5355b8ba-9189-42d2-9a0d-e975923cee3f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Improve annotation and aggregation
Hi Russell, Thanks for the response. Clearly I don't have enough time to prove my eligibility to pull it off. Guess I will hang around here outside GSoC and look forward to contributing till the extent of my capabilities :). Regards, Nimesh Ghelani On Friday, May 3, 2013 7:00:33 AM UTC+5:30, Russell Keith-Magee wrote: > > > On Fri, May 3, 2013 at 4:31 AM, nimesh ghelani >> 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.
Re: Improve annotation and aggregation
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 ghelaniwrote: > >> 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.
Re: Improve annotation and aggregation
On Fri, May 3, 2013 at 4:31 AM, nimesh ghelaniwrote: > 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.
Improve annotation and aggregation
Hey, Will like reviews on my proposal https://gist.github.com/nims11/dbd2f52677377eb60c07 Thanks and Regards, Nimesh Ghelani -- 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.