| | 1 | '''Your Name''' |
| | 2 | |
| | 3 | '''Your e-mail address and google id.''' |
| | 4 | |
| | 5 | '''Your Project's Title''' |
| | 6 | |
| | 7 | '''Abstract''' |
| | 8 | |
| | 9 | A short description. |
| | 10 | |
| | 11 | (The rest should be entered in the "detailed description" box.) |
| | 12 | |
| | 13 | '''Benefits to the Parrot VM and Open Source Community''' |
| | 14 | |
| | 15 | Who will benefit from your project and in what ways? Describe the |
| | 16 | likely user-base and what means they might currently be using to |
| | 17 | accomplish the same ends. Are you proposing an incremental |
| | 18 | improvement, a fundamentally new approach, or an aggregation of |
| | 19 | existing tools/ideas? |
| | 20 | |
| | 21 | |
| | 22 | '''Deliverables''' |
| | 23 | |
| | 24 | Describe the quantifiable results and goals. Be as specific as possible. |
| | 25 | Seriously, give more details than you think are necessary. |
| | 26 | |
| | 27 | |
| | 28 | '''Project Details''' |
| | 29 | |
| | 30 | You can't be too detailed. Describe prior art and the concepts on |
| | 31 | which your project is based. What is new or different about your |
| | 32 | approach which wasn't done/possible before? Do you have any |
| | 33 | preliminary findings or results which suggest that it is possible and |
| | 34 | likely to succeed? |
| | 35 | |
| | 36 | |
| | 37 | Note any uncertainties or aspects which depend on further research or |
| | 38 | experiments. What is your plan for dealing with snags, unforeseen |
| | 39 | difficulties, or setbacks? How useful will your results be if (when) |
| | 40 | not everything works exactly as planned? |
| | 41 | |
| | 42 | |
| | 43 | '''Project Schedule''' |
| | 44 | |
| | 45 | What are the milestones? Be sure to include dates which are |
| | 46 | compatible with the GSoC timeline. You must have a detailed |
| | 47 | description of what you plan to do each week of the Summer of Code. |
| | 48 | |
| | 49 | |
| | 50 | '''References and Likely Mentors''' |
| | 51 | |
| | 52 | Which managers and/or likely mentors have you contacted about your |
| | 53 | plans? Who was the most helpful? Have any of them offered to mentor |
| | 54 | your project? |
| | 55 | |
| | 56 | |
| | 57 | '''License''' |
| | 58 | |
| | 59 | All Parrot projects should use the Artistic 2.0 license. |
| | 60 | |
| | 61 | '''Bio''' |
| | 62 | |
| | 63 | Who are you? What makes you the best person to work on this project? |
| | 64 | What experience do you have with Parrot and other Open Source projects? |
| | 65 | What development tools and methods do you use? Have you previously |
| | 66 | been responsible (either as an employee/volunteer/student) for a |
| | 67 | project of this size? |
| | 68 | |
| | 69 | |
| | 70 | '''Eligibility''' |
| | 71 | |
| | 72 | Are you an eligible student and do you meet google's legal requirements? |
| | 73 | Do you have the paperwork to prove it? (Note that you only have to |
| | 74 | prove it to Google, but we want to be sure that paperwork will not |
| | 75 | interfere with your project after it has been selected.) |
