There is probably a summer's worth of work to do outside of the work that's already happening, so if you want to add something to the ideas page, that sounds good to me.
On Saturday, March 4, 2017 at 12:52:01 AM UTC-5, akki wrote: > > @Josh Absolutely correct. I meant since this involves a lot of things (a > couple of them are listed by Markus on the ticket itself) to do, they can > use a helping hand from a student developing full-time. > It's just a suggestion of mine, they are doing an incredible job and it's > totally their call (they can mentor the project as well since they have > already come so far with the ticket). :) > > Other than that there are many more things related to indexes that are > remaining like implementing a RenameIndex migration operation > <https://code.djangoproject.com/ticket/27064>, making db_index use class > based indexes under the hood (2nd point of the post mentioned in my last > mail), deprecating index_together > <https://code.djangoproject.com/ticket/27236>, bring indexes under > inspectdb <https://code.djangoproject.com/ticket/27060>, etc. which the > students can involve in there project. There are even more things to do > related to db-indexes than these, checkout the tickets having > "db-indexes" in their keywords > <https://code.djangoproject.com/query?status=assigned&status=new&keywords=~db-index&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id> > > for them. > > This project can be thought more of getting "Django indexes into Spartan > mode" than just "extending expressions into indexes" as I had called it > earlier, as it would power Django to do much more with indexes via class > based indexes. So if it looks good to the community this can be included in > the ideas page of Django's GSoC page. > > On Saturday, 4 March 2017 07:33:57 UTC+5:30, Josh Smeaton wrote: > >> I think Markus is currently working on this idea, along with Ian Foote, >> who has contributed some precursor work to make the idea possible >> (deconstructed expressions). The current PR is >> https://github.com/django/django/pull/8056 >> >> On Saturday, 4 March 2017 05:39:11 UTC+11, akki wrote: >>> >>> Hi >>> >>> This is in regards of this thread that was posted a few days back - >>> https://groups.google.com/forum/#!topic/django-developers/8qvrKfZaP2o >>> >>> I think "extending support for expressions into indexes" would make a >>> good candidate for the ideas page. This post >>> <https://groups.google.com/d/msg/django-developers/3c8AvB3X6mk/gbkbbwEuCAAJ> >>> by >>> Josh mentions steps to be followed to accomplish this task in a nutshell >>> (1st point had been completed in last year's GSoC). The ticket for the same >>> is https://code.djangoproject.com/ticket/26167. >>> For the complexity of this task I would suggest that it's between >>> medium-hard as it requires good knowledge about how both expressions and >>> class based indexes work in Django. >>> As far as mentoring the project is concerned I am currently not in a >>> situation to state if I'll be free for the task after a couple of months so >>> can't commit on that right now. I'll definitely help out the student with >>> any queries if anyone does pick up this project this year. >>> >>> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/a6dcdd5c-8fcc-4bbe-8023-707eccf51b1c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
