Task ideas for Google Code-in/Russian
< Task ideas for Google Code-in
Jump to navigation
Jump to search
Revision as of 15:20, 7 November 2011 by Francis Tyers (talk | contribs) (→Что это Google Code-In ?)
http://google-melange.appspot.com/gci/homepage/google/gci2011
Что это Google Code-In ?
Google Code-In is a contest held by Google to introduce pre-university students to the many kinds of contributions that make open-source software development possible. It runs from the 21st November, 2011 to the 16th January, 2012. We invite students from all over the world to produce a variety of open-source code, documentation, training materials and user experience research for the organisations participating this year. These tasks include:
- Код: Tasks related to writing or refactoring code
- Документация: Tasks related to creating/editing documents
- Outreach/маркетинг: Tasks related to community management and outreach/marketing
- Гарантия качества: Tasks related to testing and ensuring code is of high quality
- Исследование: Tasks related to studying a problem and recommending solutions
- Training: Tasks related to helping others learn more
- Перевод: Tasks related to localisation
- User Interface: Tasks related to user experience research or user interface design and interaction
Список задания
| Тип работы | Степень трудности | Заглавие | Описание | Время (часы) |
Менторы |
|---|---|---|---|---|---|
| код | 1. Трудное | Преобразовать существующий ресурс: Морфологический анализатор русского языка (существительные) | Take the Freeling анализатор (список морфологических форм) and convert the nouns to lttoolbox format. | 8–10 | Francis Tyers |
| код | 1. Трудное | Преобразовать существующий ресурс: Морфологический анализатор русского языка (прилагательные) | Take the Freeling анализатор (список морфологических форм) and convert the adjectives to lttoolbox format. | 8–10 | Francis Tyers |
| код | 1. Трудное | Преобразовать существующий ресурс: Морфологический анализатор русского языка (глаголы) | Take the Freeling анализатор (список морфологических форм) and convert the verbs to lttoolbox format. | 8–10 | Francis Tyers |
| перевод | 2. Нормальное | Перевести руководство HFST на русский язык | Перевести страницу Starting a new language with HFST на русский язык. | 5–8 | Francis Tyers |
| код | 3. Лёгкое | Преобразовать существующий ресурс: Reta Vortaro Русский-Эсперанто | Take the Russian-Esperanto lexicon and convert to lttoolbox format. | 2–4 | Jimregan |
| исследование | 2. Нормальное | Противопоставление: Русский язык и эсперанто | Create a set of test sentences (see various pages of 'Pending tests' and 'Regression tests' on the Wiki) for translation between Russian and Esperanto. The tests should cover as many features of the languages as possible. Some of the examples might be able to be found in a grammar, others might need to be invented. This will not involve programming, only grammatical analysis. | 4–6 | Hectoralos |
| исследование | 2. Нормальное | Противопоставление: Чувашский и русский языки | Create a set of test sentences (see various pages of 'Pending tests' and 'Regression tests' on the Wiki) for translation between Chuvash and Russian. The tests should cover as many features of the languages as possible. Some of the examples might be able to be found in a grammar, others might need to be invented. This will not involve programming, only grammatical analysis. | 4–6 | Hectoralos |
| исследование | 2. Нормальное | Противопоставление: Чувашский и татарский языки | Create a set of test sentences (see various pages of 'Pending tests' and 'Regression tests' on the Wiki) for translation between Chuvash and Tatar. The tests should cover as many features of the languages as possible. Some of the examples might be able to be found in a grammar, others might need to be invented. This will not involve programming, only grammatical analysis. | 4–6 | Hectoralos |
| исследование | 2. Нормальное | Противопоставление: Чувашский и турецкий языки | Create a set of test sentences (see various pages of 'Pending tests' and 'Regression tests' on the Wiki) for translation between Chuvash and Turkish. The tests should cover as many features of the languages as possible. Some of the examples might be able to be found in a grammar, others might need to be invented. This will not involve programming, only grammatical analysis. | 4–6 | Hectoralos |
| исследование | 3. Лёгкое | Рукой создать русскоязычный корпус с морфологическими разметками | Fix tagging errors in a piece of analysed text, for use in tagger training. This will involve taking some free text (such as from Wikipedia), running it through the analyser and tagger, and replacing incorrect analyses with the correct one. It may be preferable to use LanguageTool's tagger. | 2–4 | Jimregan |
