Difference between revisions of "Task ideas for Google Code-in"
Firespeaker (talk | contribs) |
Firespeaker (talk | contribs) |
||
(14 intermediate revisions by 2 users not shown) | |||
Line 83: | Line 83: | ||
{{Taskidea |
{{Taskidea |
||
|type=code |
|type=code |
||
|mentors=JNW, wei2912, padth4i |
|mentors=JNW, wei2912, padth4i, popcorndude |
||
|title=Use apertium-init to bootstrap a new language pair |
|title=Use apertium-init to bootstrap a new language pair |
||
|description=Use the [[Apertium-init]] script to bootstrap a new translation pair between two languages which have monolingual modules already in Apertium. To see if a translation pair has already been made, search our repositories on [https://github.com/apertium/ github], and especially ask on IRC. Add 100 common stems to the dictionary. Your submission should be in the form of a repository on github that we can fork to the Apertium organisation. |
|description=Use the [[Apertium-init]] script to bootstrap a new translation pair between two languages which have monolingual modules already in Apertium. To see if a translation pair has already been made, search our repositories on [https://github.com/apertium/ github], and especially ask on IRC. Add 100 common stems to the dictionary. Your submission should be in the form of a repository on github that we can fork to the Apertium organisation. |
||
Line 93: | Line 93: | ||
{{Taskidea |
{{Taskidea |
||
|type=code |
|type=code |
||
|mentors=JNW, wei2912, padth4i |
|mentors=JNW, wei2912, padth4i, popcorndude |
||
|title=Use apertium-init to bootstrap a new language module |
|title=Use apertium-init to bootstrap a new language module |
||
|description=Use the [[Apertium-init]] script to bootstrap a new language module that doesn't currently exist in Apertium. To see if a language is available, search our repositories on [https://github.com/apertium/ github], and especially ask on IRC. Add enough stems and morphology to the module so that it analyses and generates at least 100 correct forms. Your submission should be in the form of a repository on github that we can fork to the Apertium organisation. [[Task ideas for Google Code-in/Add words from frequency list|Read more about adding stems...]] |
|description=Use the [[Apertium-init]] script to bootstrap a new language module that doesn't currently exist in Apertium. To see if a language is available, search our repositories on [https://github.com/apertium/ github], and especially ask on IRC. Add enough stems and morphology to the module so that it analyses and generates at least 100 correct forms. Your submission should be in the form of a repository on github that we can fork to the Apertium organisation. [[Task ideas for Google Code-in/Add words from frequency list|Read more about adding stems...]] |
||
Line 103: | Line 103: | ||
{{Taskidea |
{{Taskidea |
||
|type=code |
|type=code |
||
|mentors=JNW, sevilay, Unhammer, marcriera, padth4i, Oguz |
|mentors=JNW, sevilay, Unhammer, marcriera, padth4i, Oguz, popcorndude |
||
|title=Write 10 lexical selection for an existing translation pair |
|title=Write 10 lexical selection for an existing translation pair |
||
|description=Add 10 lexical selection rules to an existing translation pair. Submit your work as a github pull request to that pair. [[Task ideas for Google Code-in/Add lexical-select rules|Read more...]] |
|description=Add 10 lexical selection rules to an existing translation pair. Submit your work as a github pull request to that pair. [[Task ideas for Google Code-in/Add lexical-select rules|Read more...]] |
||
Line 113: | Line 113: | ||
{{Taskidea |
{{Taskidea |
||
|type=code |
|type=code |
||
|mentors=JNW, Unhammer, padth4i, Oguz |
|mentors=JNW, Unhammer, padth4i, Oguz, popcorndude |
||
|title=Write 10 constraint grammar rules for an existing language module |
|title=Write 10 constraint grammar rules for an existing language module |
||
|description=Add 10 constraint grammar rules to an existing language module for a language that you know. Submit your work as a github pull request to that pair. [[Task ideas for Google Code-in/Add constraint-grammar rules|Read more...]] |
|description=Add 10 constraint grammar rules to an existing language module for a language that you know. Submit your work as a github pull request to that pair. [[Task ideas for Google Code-in/Add constraint-grammar rules|Read more...]] |
||
Line 232: | Line 232: | ||
|tags=evaluation |
|tags=evaluation |
||
|title=Evaluate an existing apertium pair %AAA% to %BBB% on a text |
|title=Evaluate an existing apertium pair %AAA% to %BBB% on a text |
||
|description= Pick an existing apertium pair and get a parallel text for that language pair. Translate %AAA% to %BBB% and evaluate the translation using an automatic evaluation metric like BLEU or/and evaluate it manually |
|description= Pick an existing apertium pair and get a parallel text for that language pair. Translate %AAA% to %BBB% and evaluate the translation using an automatic evaluation metric like BLEU or/and evaluate it manually. [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Evaluation_of_translation_of_an_existing_pair Read more]... |
||
}} |
}} |
||
Line 248: | Line 248: | ||
|description=The arx file is where we tell the anaphora resolution algorithm which patterns to detect and score, when we want to find the antecedent of an anaphor. Add one rule in this file which can help the algorithm find out the antecedent of an anaphor - specify the pattern to detect and the positive or negative score you want to give to the noun in this pattern. See the [http://wiki.apertium.org/wiki/Anaphora_Resolution_Module documentation] of the apertium-anaphora module for help. |
|description=The arx file is where we tell the anaphora resolution algorithm which patterns to detect and score, when we want to find the antecedent of an anaphor. Add one rule in this file which can help the algorithm find out the antecedent of an anaphor - specify the pattern to detect and the positive or negative score you want to give to the noun in this pattern. See the [http://wiki.apertium.org/wiki/Anaphora_Resolution_Module documentation] of the apertium-anaphora module for help. |
||
|tags=apertium-anaphora, anaphora resolution |
|tags=apertium-anaphora, anaphora resolution |
||
|mentors=khannatanmai |
|mentors=khannatanmai, popcorndude |
||
}} |
}} |
||
Line 265: | Line 265: | ||
|tags=python, irc |
|tags=python, irc |
||
|beginner=yes |
|beginner=yes |
||
|mentors=JNW |
|mentors=JNW, popcorndude |
||
}} |
}} |
||
Line 274: | Line 274: | ||
|tags=python, irc, wiki |
|tags=python, irc, wiki |
||
|beginner=yes |
|beginner=yes |
||
|mentors=JNW |
|mentors=JNW, popcorndude |
||
}} |
}} |
||
Line 287: | Line 287: | ||
{{Taskidea |
{{Taskidea |
||
|type=documentation |
|type=documentation |
||
|mentors=JNW, flammie |
|mentors=JNW, flammie, popcorndude |
||
|title=Add comments to a dictionary defining the symbols used in it |
|title=Add comments to a dictionary defining the symbols used in it |
||
|description=Add comments to a monolingual or bilingual dictionary file (.lexc/.dix, .dix) in the symbol definitions area that clarify what each symbol stands for. Also direct the comment reader to the Apertium wiki page on symbol definitions for more information. |
|description=Add comments to a monolingual or bilingual dictionary file (.lexc/.dix, .dix) in the symbol definitions area that clarify what each symbol stands for. Also direct the comment reader to the Apertium wiki page on symbol definitions for more information. |
||
Line 296: | Line 296: | ||
{{Taskidea |
{{Taskidea |
||
|type=documentation |
|type=documentation |
||
|mentors=JNW |
|mentors=JNW, popcorndude |
||
|title=find symbols that aren't on the list of symbols page |
|title=find symbols that aren't on the list of symbols page |
||
|description=Go through the symbol definitions in Apertium dictionaries on GitHub (.lexc and .dix format), and document any symbols you don't find on the [[List of symbols]] page. This task is fulfilled by adding at least one class of related symbols (e.g., xyz_*) or one major symbol (e.g., abc), along with notes about what it means. |
|description=Go through the symbol definitions in Apertium dictionaries on GitHub (.lexc and .dix format), and document any symbols you don't find on the [[List of symbols]] page. This task is fulfilled by adding at least one class of related symbols (e.g., xyz_*) or one major symbol (e.g., abc), along with notes about what it means. |
||
Line 305: | Line 305: | ||
|type=documentation |
|type=documentation |
||
|title=document usage of the apertium-separable module |
|title=document usage of the apertium-separable module |
||
|mentors=JNW, khannatanmai |
|mentors=JNW, khannatanmai, popcorndude |
||
|description=Document which language pairs have included the [[apertium-separable]] module in its package, which have beta-tested the lsx module, and which are good candidates for including support for lsx. Add to [[Lsx_module/supported_languages|this wiki page]] |
|description=Document which language pairs have included the [[apertium-separable]] module in its package, which have beta-tested the lsx module, and which are good candidates for including support for lsx. Add to [[Lsx_module/supported_languages|this wiki page]] |
||
|tags=lsx, dictionaries, wiki |
|tags=lsx, dictionaries, wiki |
||
Line 313: | Line 313: | ||
|type=quality |
|type=quality |
||
|title=Beta-test the apertium-separable module |
|title=Beta-test the apertium-separable module |
||
|mentors=JNW, ftyers, wei2912, khannatanmai, dolphingarlic |
|mentors=JNW, ftyers, wei2912, khannatanmai, dolphingarlic, popcorndude |
||
|description= [[Lsx_module#Creating_the_lsx-dictionary|create an lsx dictionary]] in both directions for any relevant and existing language pair that doesn't yet support it (as a "separable" branch in its GitHub repository), adding 10-30 entries to it in one or both directions. Thoroughly test to make sure the output is as expected. Report bugs/non-supported features and add them to [[Lsx_module#Future_work| future work]]. Document your tested language pair by listing it under [[Lsx_module#Beta_testing]] and in [[Lsx_module/supported_languages|this wiki page]] |
|description= [[Lsx_module#Creating_the_lsx-dictionary|create an lsx dictionary]] in both directions for any relevant and existing language pair that doesn't yet support it (as a "separable" branch in its GitHub repository), adding 10-30 entries to it in one or both directions. Thoroughly test to make sure the output is as expected. Report bugs/non-supported features and add them to [[Lsx_module#Future_work| future work]]. Document your tested language pair by listing it under [[Lsx_module#Beta_testing]] and in [[Lsx_module/supported_languages|this wiki page]] |
||
|tags=lsx, dictionaries |
|tags=lsx, dictionaries |
||
Line 377: | Line 377: | ||
|beginner=no |
|beginner=no |
||
}} |
}} |
||
{{Taskidea |
|||
|type=quality, documentation, design |
|||
|mentors=* |
|||
|tags=video, tutorial |
|||
|title=Video tutorial: installing Apertium, adding to dictionary, and submitting a PR |
|||
|description=Post a video online that (1) demonstrates how to install Apertium on an operating system of your choice, (2) demonstrates how to clone and compile an Apertium translation pair of your choice, (3) shows how to add a new word to the dictionary (categorised correctly), and (4) shows how to submit the updated dictionary as a pull request to Apertium's git repository. Add a link to the video on the [http://wiki.apertium.org/wiki/Installation#Installation_Videos installation videos page] of the Apertium wiki.<br/>The title of the video should make it easy to find, and so should probably be similar to the title of this task. We recommend a screencast with voice-over posted to YouTube, but the format and venue are up to you as long as it is publicly accessible for long term. Here are [https://www.youtube.com/playlist?list=PLHldb9r6QkVFsuxlAoVS-OL32aurUOZLC some example videos] that are relevant but that could probably be improved upon.<br/>The video **does not have to be in English**; we can evaluate it in any of the following languages: %ZZZ%. Please let us know when you claim the task what language you plan to create the video in, so that we know which mentor(s) should primarily work to evaluate your task. |
|||
|multi=200 |
|||
|beginner=yes |
|||
}} |
|||
{{Taskidea |
|||
|type=quality |
|||
|mentors=mlforcada, anakuz, xavivars, fotonzade, sevilay, Unhammer, eirien, dolphingarlic, wei2912, marcriera, padth4i, Oguz, JNW, jjjppp |
|||
|tags=xml, dictionaries |
|||
|title=Identify and add 100 new entries to a bilingual dictionary |
|||
|description=Our translation systems require large lexicons so as to provide production-quality coverage of any input data. This task requires the student to add 100 new words to a bidirectional dictionary. Choose one of the language pairs listed below, and with the help of your mentor, identify some text in one of the two languages, and run the text through Apertium's translator for that language pair to identify 100 unknown forms. As needed, add the stems of these forms to the individual languages' analysers in an appropriate way so that these words are analysed correctly. Your submission should be in the form of a pull request to each of the appropriate repositories on GitHub.<br/>The language pairs we can mentor for this task are the following: %ALLPAIRS%.<br/> [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Grow_bilingual More instructions for this task here]... |
|||
|multi=40 |
|||
|dup=10 |
|||
|beginner=yes |
|||
}} |
|||
{{Taskidea |
|||
|type=quality |
|||
|mentors=mlforcada, anakuz, xavivars, fotonzade, ftyers, sevilay, eirien, dolphingarlic, wei2912, marcriera, padth4i, Oguz, JNW |
|||
|tags=xml, dictionaries |
|||
|title=Identify and add 250 new entries to a bilingual dictionary |
|||
|description=Our translation systems require large lexicons so as to provide production-quality coverage of any input data. This task requires the student to add 250 new words to a bidirectional dictionary. Choose one of the language pairs listed below, and with the help of your mentor, identify some text in one of the two languages, and run the text through Apertium's translator for that language pair to identify 250 unknown forms. As needed, add the stems of these forms to the individual languages' analysers in an appropriate way so that these words are analysed correctly. Your submission should be in the form of a pull request to each of the appropriate repositories on GitHub.<br/>The language pairs we can mentor for this task are the following: %ALLPAIRS%.<br/> [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Grow_bilingual More instructions for this task here]... |
|||
|multi=40 |
|||
|dup=10 |
|||
|beginner=no |
|||
}} |
|||
{{Taskidea |
|||
|type=quality |
|||
|mentors=fotonzade, JNW, ftyers, anakuz, xavivars, mlforcada, shardulc, sevilay, Unhammer, dolphingarlic, wei2912, marcriera |
|||
|tags=xml, dictionaries |
|||
|title=Post-edit 500 sentences of a public domain text |
|||
|description=Many of our systems benefit from statistical methods used with (ideally public domain) bilingual data. For this task, you need to translate a public domain text using an available machine translation system (Apertium preferred) and clean up the translation yourself manually. Commit the source text and post-edited translation (in plain text format) to an existing (via pull request) or if needed new github repository for the language pair in dev/ or texts/ folder. The texts are subject to mentor approval.<br/>The language pairs we can hypothetically mentor for this task (pending their existence) are the following: %ALLPAIRS%. |
|||
|multi=40 |
|||
|dup=10 |
|||
|beginner=yes |
|||
}} |
|||
{{Taskidea |
|||
|type=research |
|||
|mentors=khannatanmai, sevilay, padth4i |
|||
|tags=evaluation |
|||
|title=Evaluate an existing Apertium translation pair on a text |
|||
|description= Pick an existing Apertium language pair and get a parallel text for that language pair. Translate the text using the Apertium translation pair and evaluate the translation using an automatic evaluation metric like BLEU and/or evaluate it manually.<br/>The language pairs we can mentor for this task (pending their existence) are the following: %ALLPAIRS%.<br/>[http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Evaluation_of_translation_of_an_existing_pair Read more]... |
|||
|multi=40 |
|||
|dup=10 |
|||
}} |
|||
<!-- {{Taskidea |
|||
|type=quality |
|||
|mentors=* |
|||
|tags=localisation |
|||
|title=Complete website localisation in a language not fully localised |
|||
|description= |
|||
|multi= |
|||
}} --> |
|||
<!-- NEW TASKS BELOW --> |
|||
</table> |
</table> |
||
Line 405: | Line 472: | ||
| m-alpha || eng, fra, byv |
| m-alpha || eng, fra, byv |
||
|- |
|- |
||
| popcorndude || eng, spa |
| popcorndude || eng, spa, cym, heb |
||
|- |
|- |
||
| sevilay || eng, ara, tur, kaz, aze, tat, gag, uig, uzb, crh, kum |
| sevilay || eng, ara, tur, kaz, aze, tat, gag, uig, uzb, crh, kum |
Latest revision as of 06:23, 5 December 2019
Contents |
This is the task ideas page for Google Code-in, here you can find ideas on interesting tasks that will improve your knowledge of Apertium and help you get into the world of open-source development.
The people column lists people who you should get in contact with to request further information. All tasks are 2 hours maximum estimated amount of time that would be spent on the task by an experienced developer, however:
- this is the time expected to take by an experienced developer, you may find that you spend more time on the task because of the learning curve.
Categories:
- code: Tasks related to writing or refactoring code
- documentation: Tasks related to creating/editing documents and helping others learn more
- research: Tasks related to community management, outreach/marketting, or studying problems and recommending solutions
- quality: Tasks related to testing and ensuring code is of high quality.
- design: Tasks related to user experience research or user interface design and interaction
Clarification of "multiple task" types
- multi = number of students who can do a given task (GCI's "max instances")
- dup = number of times a student can do the same task
You can find descriptions of some of the mentors here.
Task ideas[edit]
The current task ideas here are for 2019. See Talk:Task ideas for Google Code-in for task ideas from previous years.
Mentors[edit]
These are languages that can be substituted for AAA and/or BBB for tasks each mentor is listed to mentor above.
If you do not see your language here, ask. We may be able to mentor or find you a mentor.
Mentor | Languages |
---|---|
ftyers | eng, spa, cat, fra, nor, rus, por, swe, tur, gag, aze |
JNW | eng, spa, fra, rus, tur, gag, aze, kaz, kir, kaa, tat, bak, kum, nog, kaa, uzb, uig, crh, khk, yid |
anakuz | grn, spa, por, rus |
fotonzade | eng, tur, aze, uig, tat, crh, kmr, ckb, fas |
xavivars | cat, spa, eng, fra |
Unhammer | nno, nob, swe, dan, fao, sme, ovd |
shardulc | eng, fra, mar, hin, urd, kan |
m-alpha | eng, fra, byv |
popcorndude | eng, spa, cym, heb |
sevilay | eng, ara, tur, kaz, aze, tat, gag, uig, uzb, crh, kum |
eirien | sah, rus, eng |
khannatanmai | eng, hin |
flammie | fin, krl, olo, hun, nio, kpv, mdf, tlh, fra, swe, eng, est, ekk, vro |
dolphingarlic | afr, deu, eng |
wei2912 | eng, zho |
marcriera | cat, spa, eng, ron |
padth4i | eng, mal, hin |
Oguz | eng, tur, uig, aze, crh |
mlforcada | eng, cat, eus, fra, por, glg, spa, gle, bre |
ayushjain | eng, hin |
jjjppp | eng, lat |
Counts[edit]
Last updated by Firespeaker (talk) 07:30, 28 October 2019 (CET).
Category | Count |
---|---|
code | 16 |
documentation | 4 |
research | 11 |
quality | 8 |
design | 2 |
Total | 33 |