Intro + A few questions about Formset Improvements

[Amith Tallanki]

A little late to the party but I hope to make for lost time.

Hi,

I'm Amith, currently a fourth year student at Dayananda Sagar College Of Engineering. I was hoping to work with Django as my GSoC project if my proposal is accepted. I'll keep the intro short, here are my credentials :
Linkedin : LinkedIn
Resume : Resume

I have started working on a few byte sized bugs to go along with my proposal after going through the required documentation. However, I do have the following questions :
1. How many bugs does your average applicant solve for his/her proposal to considered amazing?
2. Does every project in the GSoC Ideas list page get a slot?
3. What level of documentation will you be requiring for Formset Improvements project? (Is a mere mixture of well commented code and pseudo logic okay or do you require detailed workflow diagrams?)
4. What kind of model will the mentor be expecting us to follow/implement? (like Scrum, Kanban any others)?
5. I'm a little embarrassed to say I haven't worked with formsets in Django but am taking the steps to rectify that asap, however, the project description has confused me a little. Does it require the formation of new structures that make the implementation of formset architecture simple or does it require new documentation to explain the current work around?

Sorry for the long winded questions. :P

Cheers,

Amith

[Tim Graham]

Hi, I'll answer your questions inline:

1. How many bugs does your average applicant solve for his/her proposal to considered amazing?

The number of bugs isn't relevant as the amount of work per bug or feature varies greatly. The important thing is that the proposal has a reasonable timetable with 12 weeks worth of work.
 

2. Does every project in the GSoC Ideas list page get a slot?

In the past couple years we've been able to accept all the good proposals we've received.
 

3. What level of documentation will you be requiring for Formset Improvements project? (Is a mere mixture of well commented code and pseudo logic okay or do you require detailed workflow diagrams?)

The amount of documentation should be on par with any major feature in Django. Take a look through past commits and our contributing guidelines to get a sense for it.
 

4. What kind of model will the mentor be expecting us to follow/implement? (like Scrum, Kanban any others)?

I haven't used any formal system when I mentored in the past. At least a weekly checkin with your mentor through email, video chat, or IRC discussion is common.
 

5. I'm a little embarrassed to say I haven't worked with formsets in Django but am taking the steps to rectify that asap, however, the project description has confused me a little. Does it require the formation of new structures that make the implementation of formset architecture simple or does it require new documentation to explain the current work around?

I'm not sure what the solution will look like but presumably there's some code to write as a project consisting solely of documentation doesn't qualify for Google Summer of Code under Google's guidelines.