On Mon, Mar 7, 2011 at 4:28 PM, Vivek Narayanan <[email protected]> wrote: > ... > In the run up to May 23rd, I'll be familiarizing myself with the > codebase and community practices of Django, examining all the > integration points and looking at the best practices of serialization. > > Week 1: I'll be implementing a basic skeletal structure for the > serializer, which will set the stage for the rest of the project. > Week 2: Implementation of the deserializer. > Week 3: I'll add support for the metadata methods as discussed above. > Week 4: Support for datatype conversion and the unicode conversion > class methods. > Week 5: Add support for string templates and output formats. > Week 6: Add support for 'modes' as in JSON, XML, YAML etc, complete > the deserializer. > Week 7: Implement serialization of related models, M2M fields, foreign > keys and nesting depth. > Week 8: Add support for ``extras`` and ``exclude`` parameters in the > call to serialize(). Modify ``fields`` parameter as described above. > Weeks 9-10: Check for bugs, fix them and write documentation with many > examples. > Weeks 11-12: Refine the project and its documentation. > > I'll be spending 40-45 hours a week on average. > > Sincerely, > Vivek Narayanan >
No offence meant here Vivek, but when I'm speccing something out or reading a spec, if there is a block of work that says 'Implement <blah>, 1 week', then I know this hasn't been thought out completely, and that '1 week' could be anything from 45 minutes to 3 months. The reason why software projects take regularly take longer than anticipated is often because the design and thought behind the design was not complete. Ideally you can start breaking down into discrete tasks, each of which shouldn't take longer than 4 hours, which is the largest block of time you should deal with in my experience. Looking at it like that, and assuming a 40 hour week, and 12 weeks of GSoC, you've got 120 units to can account for. Splitting down your project into small chunks will also demonstrate to people reading your proposal that you understand the subject matter, and they can have a high confidence of the project being delivered. Weeks 9-10 made me smile though - no bug fixes allowed in the other weeks? :) Cheers Tom -- 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.
