| | 1 | = Hints for Successful Proposals = |
| | 2 | Historically, the majority of students who have been awarded projects for work on Boost engage the community (participate on the mailing list) prior to submitting an application and write good proposals. |
| | 3 | |
| | 4 | == Engage the Community == |
| | 5 | Join the mailing list. Talk about what you want to do. If we know you're willing to get involved, then we'll review your proposal more favorably. |
| | 6 | |
| | 7 | == What Makes a Good Proposal? == |
| | 8 | Writing good proposals can be difficult and takes practice. Remember to be ''precise'', ''concise'', and ''professional'' in your proposal. |
| | 9 | |
| | 10 | * Write Precisely - Be very specific about the project you are proposing. Don't be vague. Say what you're proposing to do early the text of your submission. Demonstrate that you understand the requirements, design space, and solution space of you proposal by seeing what others have done before. Including notes on related projects and their potential impact on your work will convince |
| | 11 | |
| | 12 | * Write Concisely - Only write about the work you are proposing to do and work related to your proposal. Telling us that you placed highly in a programming competition doesn't necessarily demonstrate your qualifications with respect to your project. |
| | 13 | |
| | 14 | * Write Professionally - Writing a GSoC proposal is no different than applying for a job. Emoticons do not belong in job applications. |
