Hi Tim Thanks for the feedback.
Instead of aiming for one huge patch to be merged at the end of the summer, > I'd suggest to think about whether you can break up the work in chunks that > can be merged incrementally. This should decrease the risk that comes with > a huge patch going stale and makes code review much easier. > Yes, I see how that would be useful in the long run. Although I had made the timeline keeping in mind that the work is done in a progressive way but it would definitely be good to see that this is clearly (and more explicitly) reflected in the proposal as well. Will update my proposal ASAP to incorporate this change. > It's helpful if you can add your other commitments for the summer such as > holidays, vacations, etc. > To be honest, there aren't any commitments I have for these summers. I would be having my breaks from college and am pretty much free to work on this. I'll to see if there's anything else worth mentioning in the proposal. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/743c2cef-51b1-464a-9915-0c6695c46f4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
