I had a short look over the docs. They look good.
The sketch of a detailed plan in the proposal template is nice since students usually don't plan ahead enough.
I would like to add some general advice for students though. At MDAnalysis we have some information
that explains the programming experience we expect as well a communication quidelines and two simple
rules when a student will fail the evaluation, 1. have regular contact with mentor 2. have some code
commited to master/develop by the end of the summer. See our Wiki
https://github.com/MDAnalysis/mdanalysis/wiki/Google-Summer-Of-Code#am-i-experienced-enough I actually liked to use them since they make the decision of pass/fail easier and more transparent for
everyone involved.
About general plans. I usually have time in the evenings after 8 (UTC +1). It would be nice to now who
else would be an admin since we need a minimum of 2 and how you handle communication and
distribution of the slots to the organizations you are an umbrella for. The python org we had last year
had some clear rules and it's own timeline for management.
BTW do you also act as an umbrella for projects that aren't affiliated with numFOCUS?
best Max