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 <[email protected]<javascript:> > > 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&status=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 [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/03ee95a1-3964-40be-a7ee-f97a19ce1b0e%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
