Niall Douglas
I hate to be a bore, but I'd actually say "with full unit testing and documentation" for every single item individually. That's because people tend to scan GSoC proposals quickly, not really reading it. Remember we get in about 120 proposals each year.
Done.
What follow is a list of optional tasks I would like to complete if I have the time. Again, each task implies full unit testing and documentation.
Add "and in consultation with my mentor(s)". And again mention the unit testing and documentation every item.
Done.
Slightly change this: make the period from the start of GSoC up to C++Now being preparing your GSoC for presentation to the Boost community at C++Now (explain this is "the Boost conference"), and for which you'll be working 40 hours a week except where exams intrude.
Done.
The only factor limiting my availability is that I would like to take a vacation of perhaps one week or so during the summer. However, if I am not required to be super-available between the "pencils down" date and the final results announcement, then I can take my vacation at that time.
I'd delete any mention of vacations if I were you.
Alright, then I'll hope my mentor is indulgent.
With the above changes, I think you're ready to submit a proposal.
Thank you for your help. The final proposal is at [1] if someone wants to read it. Comments are still welcome; otherwise I'll send the application in a couple of days. Louis [1]: https://gist.github.com/ldionne/d05528280db79105e30d