| | 1 | == INSTRUCTIONS FOR ADDING SUGGESTED PROPOSALS == |
| | 2 | |
| | 3 | Please follow the following proposal structure. |
| | 4 | |
| | 5 | === No. Title === |
| | 6 | Potential mentors: names |
| | 7 | |
| | 8 | ==== Background ==== |
| | 9 | Explanation of proposal background, history etc with hyperlinks. |
| | 10 | |
| | 11 | ==== GSoC project proposal ==== |
| | 12 | Bullet points of items to complete for the GSoC. |
| | 13 | |
| | 14 | ==== Potential project extension funded by Boost ==== |
| | 15 | Not as much detail as the GSoC proposal itself, but enough detail that such an extension could be specced out. |
| | 16 | |
| | 17 | If there is no good extension, simply say N/A here. |
| | 18 | |
| | 19 | ==== Programming competency test ==== |
| | 20 | Some code for them to write to prove they can program sufficiently. Ideally it should be a small part of the proposal itself modifying real Boost library code, but there is nothing wrong with an actual exam paper, except that maybe they might cheat if you give them too much time and flexibility in when to do it, so if setting an exam question make sure you say here it will be written and set to interested students on some date after GSoC applications close and they'll get X days to finish it. |
| | 21 | |
| | 22 | How they submit their results is up to you. They can append them to their project proposal, or provide a gist, or email them to you for marking, or whatever. |
| | 23 | |
| | 24 | If there is no programming competency test, please add your proposal to the second section below the special section for proposals without competency testing. |
