On Thu, Apr 25, 2013 at 3:00 AM, Andrew Godwin <[email protected]> wrote:
> Hi Damian, > > We don't generally accept GSOC projects that are just a bit grab bag of > problems - this is looking a little bit like that. I'd like to see a better > breakdown of what kind of time each ticket would take and what your > planning schedule would be - in particular, I'd like to make sure you have > roughly 12 full weeks worth of work, as some of these tickets are quite > easy to fix. > > It would also be nice to see you pick fewer issues but ones which were > more difficult - a past security GSOC just focused on three or four main, > difficult problems, and while not all got done, it developed in a > reasonable way. > I agree with Andrew - we're not just looking for "fix a bunch of bugs" as a GSoC project. Don't get me wrong - bug fixes are good, but you're in a unique position of having a 12 week dedicated period for working on Django. This is an opportunity to fix a problems at a deep level, not just skim over a lot of surface. However, your ticket triage isn't necessarily all a waste. An alternative approach to your proposal would be to identify broad or systematic problems, and use the tickets as exemplars of how that problem manifests. An example of this (that doesn't come from GSoC) was Ben Firshman's handling of syndication back in the days of Django 1.1. Ben identified that there were a lot of open bugs in the syndication framework, and he analysed the trends and causes of those bugs -- for the most part, IIRC, subtle variations between Atom and RSS formats. He then identified that the structure of the existing code was the cause of these problems, and proposed an alternative structure that would address these problems - and probably many more related problems. So - instead of just proposing a bunch of tickets to fix, analyse why those tickets exist. Are there recurring themes? Are we making the same mistake in multiple parts of the codebase? Is it possible that the same problem is being made somewhere else, but not being reported? 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
