Difference between revisions of "Google Summer of Code/Application 2010"
Jump to navigation
Jump to search
Line 35: | Line 35: | ||
* We expect students to contact us using IRC or e-mail; we will make sure we get the following information from all applicants: |
* We expect students to contact us using IRC or e-mail; we will make sure we get the following information from all applicants: |
||
* Name, e-mail address, and other information that may be useful for contact |
* Name, e-mail address, and other information that may be useful for contact |
||
* Why is it you are interested in machine translation? |
* Why is it you are interested in machine translation? |
||
* Why is it that |
* Why is it that you are interested in the Apertium project? |
||
* Which of the published tasks are you interested in? What do you plan to do? |
* Which of the published tasks are you interested in? What do you plan to do? |
||
* Applicants should also include a one- or two-page proposal, including a title, reasons why Google and Apertium should sponsor it, a description of how and who it will benefit, and a detailed work plan including, if possible, a brief schedule with milestones and deliverables. Include time needed to think, to program, to document and to disseminate. |
* Applicants should also include a one- or two-page proposal, including a title, reasons why Google and Apertium should sponsor it, a description of how and who it will benefit, and a detailed work plan including, if possible, a brief schedule with milestones and deliverables. Include time needed to think, to program, to document and to disseminate. |
||
* List your skills and give evidence of your qualifications. Tell us what is current field of study, major, etc. |
* List your skills and give evidence of your qualifications. Tell us what is current field of study, major, etc. |
||
* Convince us that you can do the work. In particular we would like to know whether you have programmed before in open-source projects. |
* Convince us that you can do the work. In particular we would like to know whether you have programmed before in open-source projects. |
||
* Please list any non-Summer-of-Code plans you have for the Summer, especially employment and class-taking. Be specific about schedules and time commitments. we would like to be sure you have at least 20 free hours a week to develop for our project. |
* Please list any non-Summer-of-Code plans you have for the Summer, especially employment and class-taking. Be specific about schedules and time commitments. we would like to be sure you have at least 20 free hours a week to develop for our project. |
||
Revision as of 06:39, 8 March 2010
Application
- 1. Describe your organization.
- 2. Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating?
- 3. Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
- Apertium participated in GSoC 2009. We finally got 9 slots, and 8 out of the 9 students selected succeeded.
- The report we have in [1] is unfortunately incomplete
- 4. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
- n/a
- 5. What license(s) does your project use?
- GNU GPL 2.0/3.0
- 6. What is the URL for your ideas page?
- 7. What is the main development mailing list for your organization?
- apertium-stuff@lists.sourceforge.net
- 8. What is the main IRC channel for your organization?
#apertium
onirc.freenode.net
- 9. Does your organization have an application template you would like to see students use? If so, please provide it now.
- We expect students to contact us using IRC or e-mail; we will make sure we get the following information from all applicants:
* Name, e-mail address, and other information that may be useful for contact * Why is it you are interested in machine translation? * Why is it that you are interested in the Apertium project? * Which of the published tasks are you interested in? What do you plan to do?
- Applicants should also include a one- or two-page proposal, including a title, reasons why Google and Apertium should sponsor it, a description of how and who it will benefit, and a detailed work plan including, if possible, a brief schedule with milestones and deliverables. Include time needed to think, to program, to document and to disseminate.
* List your skills and give evidence of your qualifications. Tell us what is current field of study, major, etc. * Convince us that you can do the work. In particular we would like to know whether you have programmed before in open-source projects. * Please list any non-Summer-of-Code plans you have for the Summer, especially employment and class-taking. Be specific about schedules and time commitments. we would like to be sure you have at least 20 free hours a week to develop for our project.
- 10. Who will be your backup organization administrator?
- Gema Ramírez Sánchez
- 11. What criteria did you use to select these individuals as mentors? Please be as specific as possible.
- 12. What is your plan for dealing with disappearing students?
- 13. What is your plan for dealing with disappearing mentors?
- 14. What steps will you take to encourage students to interact with your project's community before, during and after the program?
- 15. What will you do to ensure that your accepted students stick with the project after GSoC concludes?