GSoC query

[anubhav joshi]

Well I am thinking to work on aggregates and annotation, and improving the error messages part.

I just want to know if these are still open.

And what is the procedure if more than one student submit similar proposals or what if one submits it before then whether it remains open for another?

Can we start submitting proposals before March 10 or do we have to wait till then?

[Christopher Medrela]

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

[Aymeric Augustin]

On 8 févr. 2014, at 22:02, Christopher Medrela <chris....@gmail.com> wrote:

> AFAIK, there is no problem if there is more than one student working on the same idea.

In practice, I don’t think we would allocate two slots to the same idea. However, an proposal that wasn’t thoroughly discussed on this mailing-list has almost no chance of being selected. That makes it easy to detect possible conflicts. For this year’s GSoC, I haven’t seen any serious proposal yet.

--
Aymeric.

[Russell Keith-Magee]

On Sun, Feb 9, 2014 at 5:02 AM, Christopher Medrela <chris....@gmail.com> wrote:

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. 

They're definitely still "open" in the sense that the problems still exist, and the projects haven't been allocated to a specific student.

 

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.

There's no limit on multiple students working on the same *proposal*, but ultimately, we're not going to pick two students to work on the same project. This is for administrative reasons -- GSoC requires us to evaluate students as individuals, and if two students are collaborating on a project, or if one student's work is dependent on another in some way, then this becomes a lot more difficult. 

  

Yours,

Russ Magee %-)

[anubhav joshi]

Apart from the issues and tickets mentioned in the idea pages and some other tickets/issues which I have found is there anything that anyone would suggest for working on the aggregation/annotation part, like if there  is any issue which hasn't been picked up in tickets or anything else,if something new has occurred to anyone.

Anubhav Joshi

[Josh Smeaton]

I've been working on aggregation lately, and have opened up a PR https://github.com/django/django/pull/2184

I think the implementation is promising, but it hasn't been vetted by a core contributor yet. I've also begun work on https://github.com/jarshwah/django/commits/nonaggregate-annotations, based on the above pull request. I think both of these branches together solve (or will solve) most of the issues relating to the existing GSOC idea. Unfortunately, due to the timing of my work, it's unlikely to be reviewed until after the 1.7 release - sometime after March (Beta) or May (Release).

Are there any other tickets related to aggregation that would be a candidate for GSOC?

- Josh

[anubhav joshi]

Well I will see what I put in my proposal......it will be based on aggregation/annotation as well as improving the error message part as before...I might now look to other things as well like improving tests as well.....

[Florian Apolloner]

On Saturday, February 15, 2014 5:01:09 PM UTC+1, anubhav joshi wrote:

Well I will see what I put in my proposal......it will be based on aggregation/annotation as well as improving the error message part as before...I might now look to other things as well like improving tests as well.....

That sounds a little bit to much, the topics themselves are all in all probably three GSoC projects, covering two or more in one will most likely not lead to any success. If I were you (speaking as student), I'd hash out one in all the details and show us that you are actually up to solve one. Trying to tell us that you can solve more than one will most likely meet a bit of scepticism,  especially since noone knows you personally.

Regards,
Florian

[anubhav joshi]

I am not trying to say that I can solve all the issues myself, that is no way possible. But I had wanted to base my work on aggregation part but I think quite has been done so I just said that I would now explore other areas as well. I have no intention of telling that I could do all, I merely posted the reply to get suggesstions for those topics.

Apologies if what I wrote made you think that way.

Anubhav 

[anubhav joshi]

I need some suggestions related to improving the error message. I have gone through some tickets but I would like to know the existing issues that need to be resolved first than others, I mean those issues which need more attention.

Thanking You
Anubhav

[Russell Keith-Magee]

Hi Anubhav,

Part of the GSoC "audition" process is for you to do this analysis yourself. The GSoC wiki page lists a couple of tickets, and links to a wiki page that describes the problem in depth. We're looking for people who can take that initial direction, investigate the underlying problem, and make a concrete proposal.

We're happy to give you directions or advice on a specific proposal, but asking "what should I do" isn't the place to start.

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-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/dedfe427-76e1-42dd-a816-4c2beb2c6926%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[anubhav joshi]

Ok, actually my college exams are going on, as soon as they get over I will definitely take some action towards drafting the proposal and posting it here for review.

Thanks
Anubhav

[anubhav joshi]

I originally wanted to work on aggregates/annotation improvement in GSoC and still wish the same. The issues that I want to consider are:

Implementing arithmetic operations on aggregation/annotation.
Implementing conditional aggregates.
Fixing the errors related to the working eg. default values for aggregations/annotations, problem in using nested statements like filter() with them, etc
Adding datetime grouping to aggregation.

I have started working on the above issues. Regarding the errors part I have been able to figure out the problems.

Also I did some surfing the net regarding implementing arithmetic operations on aggregation.. I have found few ways:
1.)Adding it directly.
2.)Changing the complete implementation to f() or q() objects.

I have yet to work on the remaining issues which I surely will.

I want to know whether this will make up a good GSoC project.


Anubhav Joshi