| Version at: 01/03/2015, 16:38 vs. version at: 26/01/2016, 23:58 | ||
|---|---|---|
| 1 | 1 | # GSoC Application Requirements |
| 2 | ||
| 3 | --- | |
| 4 | ||
| 5 | **Warning**: The information on this page are not final yet. It may change in the next couple of weeks. | |
| 6 | ||
| 7 | ---- | |
| 2 | 8 | |
| 3 | 9 | We don't have a strict template for student applications. Instead, we require all applications to have answers to the following questions. Your application does not need to follow this order, use this page as a template etc. Instead, please write your application so that it is easy to read and contains information that answers all the questions in this page. |
| 4 | 10 | |
| 5 | 11 | ## Contact info |
| 6 | 12 | |
| 7 | 13 | - Name: |
| 8 | 14 | - Email address: (put a single one please) |
| 9 | 15 | - IRC/Jabber nick: |
| 10 | 16 | - Your username on tatoeba.org: |
| 11 | 17 | - GitHub username: |
| 12 | 18 | - Other contact info: |
| 13 | 19 | - Timezone: |
| 14 | 20 | - Natural languages you know: |
| 15 | 21 | |
| 16 | 22 | ## Project details |
| 17 | 23 | |
| 18 | 24 | Please provide a write-up that answers the following questions. Keep this part strictly technical and without any personal remarks. Don't include the questions. |
| 19 | 25 | |
| 20 | 26 | - In short, what your proposal is about? |
| 21 | 27 | - Why does Tatoeba need your proposal? |
| 22 | 28 | |
| 23 | 29 | - How do you plan to implement it in details? |
| 24 | 30 | - What deliverables can we expect? |
| 25 | 31 | - What kind of maintenance will your code need after GSoC? |
| 26 | 32 | |
| 27 | 33 | - What technical risks do you see with your proposal? Ie. can you anticipate any technical problems that might show up while preparing the implementation? |
| 28 | 34 | |
| 29 | 35 | - Is there any specific kind of help you expect your mentor to provide? |
| 30 | 36 | |
| 31 | 37 | ## Schedule |
| 32 | 38 | |
| 33 | 39 | Please address the following questions in this section: |
| 34 | 40 | |
| 35 | 41 | - What kind of preparations do you plan to do during the community bonding period? |
| 36 | 42 | - What is your intended weekly schedule for the work period? Don’t include “mid-term evaluation” and “final evaluation” in it since these doesn't take much time. The schedule doesn't have to be exact. |
| 37 | 43 | - What would you do if you can't finish your project on time, or you finish it way before the deadline? |
| 38 | 44 | - What risks do you see with your schedule? Ie. what problems related to your schedule can you anticipate, and how will you try to mitigate them? |
| 39 | 45 | - Do you have any other commitments during the GSoC work period other than the project itself (any exams or other school-related deadlines, holidays, vacations etc.)? Please include them in your schedule. |
| 40 | 46 | |
| 41 | 47 | ## Personal details |
| 42 | 48 | |
| 43 | 49 | Please write about yourself. Your description should answer the following questions. |
| 44 | 50 | |
| 45 | 51 | - Who are you? What skills (both relevant to the project and other computer-related) do you have? Which skills necessary for the project do you need to learn? |
| 46 | 52 | |
| 47 | 53 | - What is your experience with Tatoeba so far? |
| 48 | 54 | - Why Tatoeba and not some other organization? |
| 49 | 55 | - Why you and not someone else? |
| 50 | 56 | |
| 51 | 57 | - Do you have any non-financial motivation related to pursuing the project? |
| 52 | 58 | - Can you show us any example of code that proves you have the skills? |
| 53 | 59 | - What is your past experience in open-source/free software projects? Do you have any past GSoC experience? |
| 54 | 60 | - What is your experience in collaboration in software projects, ie. when you worked with other people on a single piece of software? |
| 55 | 61 | |
| 56 | 62 | - Are you applying to other projects for GSoC and, if so, what would be your preference if you're accepted to both? Having a stated preference helps with the deduplication process and will not impact if we accept your application or not. |
| 57 | 63 | |
| 58 | 64 | |
| diff view generated by jsdifflib | ||
Version at: 01/03/2015, 16:38
# GSoC Application Requirements We don't have a strict template for student applications. Instead, we require all applications to have answers to the following questions. Your application does not need to follow this order, use this page as a template etc. Instead, please write your application so that it is easy to read and contains information that answers all the questions in this page. ## Contact info - Name: - Email address: (put a single one please) - IRC/Jabber nick: - Your username on tatoeba.org: - GitHub username: - Other contact info: - Timezone: - Natural languages you know: ## Project details Please provide a write-up that answers the following questions. Keep this part strictly technical and without any personal remarks. Don't include the questions. - In short, what your proposal is about? - Why does Tatoeba need your proposal? - How do you plan to implement it in details? - What deliverables can we expect? - What kind of maintenance will your code need after GSoC? - What technical risks do you see with your proposal? Ie. can you anticipate any technical problems that might show up while preparing the implementation? - Is there any specific kind of help you expect your mentor to provide? ## Schedule Please address the following questions in this section: - What kind of preparations do you plan to do during the community bonding period? - What is your intended weekly schedule for the work period? Don’t include “mid-term evaluation” and “final evaluation” in it since these doesn't take much time. The schedule doesn't have to be exact. - What would you do if you can't finish your project on time, or you finish it way before the deadline? - What risks do you see with your schedule? Ie. what problems related to your schedule can you anticipate, and how will you try to mitigate them? - Do you have any other commitments during the GSoC work period other than the project itself (any exams or other school-related deadlines, holidays, vacations etc.)? Please include them in your schedule. ## Personal details Please write about yourself. Your description should answer the following questions. - Who are you? What skills (both relevant to the project and other computer-related) do you have? Which skills necessary for the project do you need to learn? - What is your experience with Tatoeba so far? - Why Tatoeba and not some other organization? - Why you and not someone else? - Do you have any non-financial motivation related to pursuing the project? - Can you show us any example of code that proves you have the skills? - What is your past experience in open-source/free software projects? Do you have any past GSoC experience? - What is your experience in collaboration in software projects, ie. when you worked with other people on a single piece of software? - Are you applying to other projects for GSoC and, if so, what would be your preference if you're accepted to both? Having a stated preference helps with the deduplication process and will not impact if we accept your application or not.
version at: 26/01/2016, 23:58
# GSoC Application Requirements --- **Warning**: The information on this page are not final yet. It may change in the next couple of weeks. ---- We don't have a strict template for student applications. Instead, we require all applications to have answers to the following questions. Your application does not need to follow this order, use this page as a template etc. Instead, please write your application so that it is easy to read and contains information that answers all the questions in this page. ## Contact info - Name: - Email address: (put a single one please) - IRC/Jabber nick: - Your username on tatoeba.org: - GitHub username: - Other contact info: - Timezone: - Natural languages you know: ## Project details Please provide a write-up that answers the following questions. Keep this part strictly technical and without any personal remarks. Don't include the questions. - In short, what your proposal is about? - Why does Tatoeba need your proposal? - How do you plan to implement it in details? - What deliverables can we expect? - What kind of maintenance will your code need after GSoC? - What technical risks do you see with your proposal? Ie. can you anticipate any technical problems that might show up while preparing the implementation? - Is there any specific kind of help you expect your mentor to provide? ## Schedule Please address the following questions in this section: - What kind of preparations do you plan to do during the community bonding period? - What is your intended weekly schedule for the work period? Don’t include “mid-term evaluation” and “final evaluation” in it since these doesn't take much time. The schedule doesn't have to be exact. - What would you do if you can't finish your project on time, or you finish it way before the deadline? - What risks do you see with your schedule? Ie. what problems related to your schedule can you anticipate, and how will you try to mitigate them? - Do you have any other commitments during the GSoC work period other than the project itself (any exams or other school-related deadlines, holidays, vacations etc.)? Please include them in your schedule. ## Personal details Please write about yourself. Your description should answer the following questions. - Who are you? What skills (both relevant to the project and other computer-related) do you have? Which skills necessary for the project do you need to learn? - What is your experience with Tatoeba so far? - Why Tatoeba and not some other organization? - Why you and not someone else? - Do you have any non-financial motivation related to pursuing the project? - Can you show us any example of code that proves you have the skills? - What is your past experience in open-source/free software projects? Do you have any past GSoC experience? - What is your experience in collaboration in software projects, ie. when you worked with other people on a single piece of software? - Are you applying to other projects for GSoC and, if so, what would be your preference if you're accepted to both? Having a stated preference helps with the deduplication process and will not impact if we accept your application or not.