On Sun, Feb 9, 2014 at 5:02 AM, Christopher Medrela <[email protected] > 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 %-) -- 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 [email protected]. To post to this group, send email to [email protected]. 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/CAJxq8490%2BsvrJeMfPPyvkUQKse0aZGUWqGum0TfdZRbeMY_dZw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
