Difference between revisions of "Google Summer of Code/Application 2013"
Jump to navigation
Jump to search
Line 22: | Line 22: | ||
;7. If you chose "veteran" in the dropdown above, please summarise your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. |
;7. If you chose "veteran" in the dropdown above, please summarise your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year. |
||
Apertium took part in GSoC in 2009, 2010, 2011 and 2012. We received 9 slots in 2009, 9 again in 2010, 11 in 2011, and 12 in 2012 although we gave one slot back to the pool, making 11. We are very happy with the results of our participation. Our main successes and challenges are described below: |
|||
Successes |
|||
* Getting useful results: |
|||
* Getting maintainable results: |
|||
* Finding new developers: |
|||
* Selecting applicants: We continued refining our selection process, and found it worked even better in 2012 than in 2011. |
|||
;8. Why is your organisation applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?* |
;8. Why is your organisation applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?* |
Revision as of 19:06, 18 March 2013
Application
- 1. Organisation name*
Apertium
- 2. Organisation description*
- 3. Organisation home page url*
- 4. Main organisation license*
GNU General Public Licence
- 5. Veteran/New*
Veteran
- 6. Backup Admin*
- 7. If you chose "veteran" in the dropdown above, please summarise your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year.
Apertium took part in GSoC in 2009, 2010, 2011 and 2012. We received 9 slots in 2009, 9 again in 2010, 11 in 2011, and 12 in 2012 although we gave one slot back to the pool, making 11. We are very happy with the results of our participation. Our main successes and challenges are described below:
Successes
- Getting useful results:
- Getting maintainable results:
- Finding new developers:
- Selecting applicants: We continued refining our selection process, and found it worked even better in 2012 than in 2011.
- 8. Why is your organisation applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?*
- 9. What is the URL for your Ideas list?*
http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code
- 10. What is the main development mailing list for your organisation?*
apertium-stuff@lists.sourceforge.net
- 11. What is the main IRC channel for your organisation?*
#apertium irc.freenode.net
- 12. What criteria did you use to select your mentors for this year's program? Please be as specific as possible.*
- 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 and during the program?*
- 15. What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?*
- 16. Are you an established or larger organisation who would like to vouch for a new organisation applying this year? If so, please list their name(s) here.