I believe if your tickets are enough work to fill 12 weeks, someone is not going to come along and complete a majority of them in the meantime. You can also add something like "I hope to work on this ticket for GSoC 2014."
On Thursday, February 27, 2014 3:57:45 PM UTC-5, anubhav joshi wrote: > > > > On Friday, February 28, 2014 2:03:10 AM UTC+5:30, Tim Graham wrote: >> >> I think it'll be better to put your analysis of each ticket on the ticket >> itself. Then when you're finished with that, put together a more high level >> overview of the analysis you've done. I think it will be easier to give >> feedback if you structure your thoughts in this way. Thanks! >> >> >> If I put my analysis on all the tickets that I have studied and analysed, > and then if someone on studying that analysis, fixes the issue then what > will I put in my proposal? I mean I have to ensure that I have sufficient > work for GSoC. How do I that ? > -- 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/5a5dfc2c-f55e-4698-a623-3249037e643b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
