On 10/03/2012, at 3:48 PM, Karthik Abinav wrote: > Hi, > > I was looking through the google summer of code 2012 wiki page and found > the "Best practices updates" problem interesting and would like to work > towards it. It would be really nice, if someone could explain in more detail > as to what exactly is expected there. I am moderately comfortable with the > code base. So, references to code and the problems along the way would also > be useful.
I'm not really sure what extra information you're looking for here. The project proposal seems fairly clear to me -- find features that have been added in recent Django release, then find all the places where Django itself (and in particular, the contrib apps) could be using that feature. Rinse and repeat until you have enough weeks to fill a 12 week project plan. Project validation (ticket #8579) and URL namespacing are two areas that have been specifically identified as candidates. However, these aren't the only areas where Django has failed to eat it's own dogfood. If you're interested in submitting a proposal for this project, your elaboration process will be to work your way through the 1.1, 1.2, 1.3 and 1.4 release notes, and find all the places where Django could make better use of it's own feature set. We're not going to just give you all the answers -- if you want us to commit to mentoring you for 3 months, you need to prove to us that you are capable of elaborating an idea and developing a proposal that is a valuable contribution, and achievable in the timeframe. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
