|
|
| Line 1: |
Line 1: |
| Jubanka:
| | See http://my.bzflag.org/w/Google_Summer_of_Code_Acceptance for a very good set of "rules" for the students. We should consider copying and adapting that. In particular, it should be absolutely mandatory for all participating students to provide updates once a week, with the clear message that failure to do so without excuse *in advance* will, after a warning, result in exclusion from GSoC. See also http://my.bzflag.org/gsoc/bzflag_gsoc2007_post_mortem.pdf -- quite cool document, maybe we can do something similar? [[User:Fingolfin|Fingolfin]] 18:14, 25 February 2008 (CET) |
| ----
| |
| * I could also mentor the software renderer of residual or the high quality mixer.
| |
| * maybe we should split the page between SoC for students and the SoC proposal.
| |
| * we could copy the open tasks page to another page and edit it, making it more focused for students. We can setup a common template, like: intro, what will a student learn, a few milestones etc. This can be brief; remember students have to propose their work.
| |
| * For our proposal. I think a few pages (perhaps <5) will do the trick. We need to fix the structure and start working on it. For the questions laid out in the application example in Soc: Questions 3-9, 11-12 are pretty straightforward. We need to pitch 1 and 2 very carefully. we also could use a template for student apps (10). Q13: short bios could be of use there. Each mentor could prepare a couple of para's with experience related to the subjects he's going to mentor. We also need to come up with a plan for 14-17. no idea there yet.
| |
| ----
| |