Apertium has moved from SourceForge to GitHub.
If you have any questions, please come and talk to us on #apertium on irc.freenode.net or contact the GitHub migration team.

Task ideas for Google Code-in

From Apertium
(Difference between revisions)
Jump to: navigation, search
(Mentors)
(Task ideas)
 
(35 intermediate revisions by 7 users not shown)
Line 18: Line 18:
   
 
'''Clarification of "multiple task" types'''
 
'''Clarification of "multiple task" types'''
* multi = number of students who can do a given task
+
* 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
 
* dup = number of times a student can do the same task
   
Line 27: Line 27:
 
'''The current task ideas here are for 2019.''' See [[Talk:Task ideas for Google Code-in]] for task ideas from previous years.
 
'''The current task ideas here are for 2019.''' See [[Talk:Task ideas for Google Code-in]] for task ideas from previous years.
   
<table class="sortable wikitable">
+
<table class="sortable wikitable" style="display: none">
 
<tr><th>type</th><th>title</th><th>description</th><th>tags</th><th>mentors</th><th>bgnr?</th><th>multi?</th><th>duplicates</th></tr>
 
<tr><th>type</th><th>title</th><th>description</th><th>tags</th><th>mentors</th><th>bgnr?</th><th>multi?</th><th>duplicates</th></tr>
   
Line 33: Line 33:
 
|type=research, quality, documentation
 
|type=research, quality, documentation
 
|title=Adopt a Wiki page
 
|title=Adopt a Wiki page
|description=Request an Apertium wiki account and adopt a wiki page by updating and fixing any issues with it. Examples of things to update might be documentation that still refers to our SVN repo (we're on GitHub now), documentation of new features, clarification of unclear things, indicating that a page no longer reflects how things are done, or updating documentation to reflect the current options and defaults of various tools.
+
|description=Request an Apertium wiki account and adopt a wiki page by updating and fixing any issues with it. Examples of things to update might be documentation that still refers to our SVN repo (we're on GitHub now), documentation of new features, clarification of unclear things, indicating that a page no longer reflects how things are done, "archiving" a page that represents deprecated information, or updating documentation to reflect the current options and defaults of various tools.
  +
|tags=wiki
  +
|mentors=*
  +
|multi=150
  +
|beginner=yes
  +
}}
  +
  +
{{Taskidea
  +
|type=research, quality, documentation
  +
|title=Test instructions on Apertium wiki
  +
|description=Find a page on the Apertium wiki that documents how to do something (hint: check the [http://wiki.apertium.org/wiki/Category:Documentation Documentation] category). Then try to follow the instructions. Check with your mentor when you get stuck. Modify the instructions as necessary. If the instructions are for something that is deprecated or no longer used by the community, either mark them as deprecated (category, banner at top of page, fix links to page) and/or modify them to match current practices.
 
|tags=wiki
 
|tags=wiki
 
|mentors=*
 
|mentors=*
Line 73: Line 73:
 
{{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 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 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 93: Line 93:
 
{{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 103: Line 103:
 
{{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 113: Line 113:
 
{{Taskidea
 
{{Taskidea
 
|type=research
 
|type=research
|mentors=anakuz, fotonzade, khannatanmai
+
|mentors=anakuz, fotonzade
 
|title=Syntactic annotation of text
 
|title=Syntactic annotation of text
 
|description=Pick a text of about 200 words and make a syntactic annotation for it according to the Universal Dependencies treebank. UD Annotatrix can be used for visualisation. Consult with your mentor about the language.
 
|description=Pick a text of about 200 words and make a syntactic annotation for it according to the Universal Dependencies treebank. UD Annotatrix can be used for visualisation. Consult with your mentor about the language.
Line 121: Line 121:
 
{{Taskidea
 
{{Taskidea
 
|type=research
 
|type=research
|mentors=JNW,ftyers, fotonzade, khannatanmai, anakuz, Oguz
+
|mentors=JNW,ftyers, fotonzade, anakuz, Oguz
 
|title=Create a UD-Apertium morphology mapping
 
|title=Create a UD-Apertium morphology mapping
 
|description=Choose a language that has a Universal Dependencies treebank and tabulate a potential set of Apertium morph labels based on the (universal) UD morph labels. See Apertium's [[list of symbols]] and [http://universaldependencies.org/ UD]'s POS and feature tags for the labels.
 
|description=Choose a language that has a Universal Dependencies treebank and tabulate a potential set of Apertium morph labels based on the (universal) UD morph labels. See Apertium's [[list of symbols]] and [http://universaldependencies.org/ UD]'s POS and feature tags for the labels.
Line 131: Line 131:
 
{{Taskidea
 
{{Taskidea
 
|type=research
 
|type=research
|mentors=JNW, ftyers, fotonzade, khannatanmai, anakuz
+
|mentors=JNW, ftyers, fotonzade, anakuz
 
|title=Create an Apertium-UD morphology mapping
 
|title=Create an Apertium-UD morphology mapping
 
|description=Choose a language that has an Apertium morphological analyser and adapt it to convert the morphology to UD morphology
 
|description=Choose a language that has an Apertium morphological analyser and adapt it to convert the morphology to UD morphology
Line 144: Line 144:
 
|description=See [[Installation]] for instructions and if you encounter any issues along the way, document them and/or improve the wiki instructions!
 
|description=See [[Installation]] for instructions and if you encounter any issues along the way, document them and/or improve the wiki instructions!
 
|tags=bash
 
|tags=bash
|mentors=ftyers, JNW, Unhammer, anakuz, Josh, fotonzade, sevilay, eirien, wei2912, padth4i
+
|mentors=ftyers, JNW, Unhammer, anakuz, Josh, fotonzade, sevilay, eirien, wei2912, padth4i, jjjppp
 
|multi=150
 
|multi=150
 
|beginner=yes
 
|beginner=yes
Line 153: Line 153:
 
|title=Write a contrastive grammar
 
|title=Write a contrastive grammar
 
|description=Document 6 differences between two (preferably related) languages and where they would need to be addressed in the [[Apertium pipeline]] (morph analysis, transfer, etc). Use a grammar book/resource for inspiration. Each difference should have no fewer than 3 examples. Put your work on the Apertium wiki under [[Language1_and_Language2/Contrastive_grammar]]. See [[Farsi_and_English/Pending_tests]] for an example of a contrastive grammar that a previous GCI student made.
 
|description=Document 6 differences between two (preferably related) languages and where they would need to be addressed in the [[Apertium pipeline]] (morph analysis, transfer, etc). Use a grammar book/resource for inspiration. Each difference should have no fewer than 3 examples. Put your work on the Apertium wiki under [[Language1_and_Language2/Contrastive_grammar]]. See [[Farsi_and_English/Pending_tests]] for an example of a contrastive grammar that a previous GCI student made.
|mentors=Mikel, JNW, Josh, xavivars, fotonzade, sevilay, khannatanmai, dolphingarlic, padth4i
+
|mentors=mlforcada, JNW, Josh, xavivars, fotonzade, sevilay, khannatanmai, dolphingarlic, padth4i
 
|tags=wiki, languages
 
|tags=wiki, languages
 
|beginner=yes
 
|beginner=yes
Line 161: Line 161:
 
{{Taskidea
 
{{Taskidea
 
|type=quality
 
|type=quality
|mentors=Mikel, anakuz, xavivars, fotonzade, sevilay, Unhammer, eirien, dolphingarlic, wei2912, marcriera, padth4i, Oguz
+
|mentors=mlforcada, anakuz, xavivars, fotonzade, sevilay, Unhammer, eirien, dolphingarlic, wei2912, marcriera, padth4i, Oguz, JNW, jjjppp
 
|tags=xml, dictionaries
 
|tags=xml, dictionaries
|title=Add 200 new entries to the bilingual dictionary of language pair %AAA%-%BBB%
+
|title=Identify and add 100 new entries to the bilingual dictionary for the %AAA%-%BBB% language pair
|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 200 new words to a bidirectional dictionary. [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Grow_bilingual Read more]...
+
|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. With the help of your mentor, identify some text in either %AAA% or %BBB% and run it through Apertium's %AAA%-%BBB% translator to identify 50 unknown forms. Add the stems of these forms to the analyser 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. [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Grow_bilingual More instructions for this task here]...
 
|multi=40
 
|multi=40
 
|beginner=yes
 
|beginner=yes
Line 171: Line 171:
 
{{Taskidea
 
{{Taskidea
 
|type=quality
 
|type=quality
|mentors=Mikel, anakuz, xavivars, fotonzade, ftyers, sevilay, eirien, dolphingarlic, wei2912, marcriera, padth4i, Oguz
+
|mentors=mlforcada, anakuz, xavivars, fotonzade, ftyers, sevilay, eirien, dolphingarlic, wei2912, marcriera, padth4i, Oguz, JNW
 
|tags=xml, dictionaries
 
|tags=xml, dictionaries
|title=Add 500 new entries to the bilingual dictionary of language pair %AAA%-%BBB%
+
|title=Identify and add 250 new entries to the bilingual dictionary for the %AAA%-%BBB% language pair
|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 500 new words to a bidirectional dictionary. [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Grow_bilingual Read more]...
+
|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. With the help of your mentor, identify some text in either %AAA% or %BBB% and run it through Apertium's %AAA%-%BBB% translator to identify 50 unknown forms. Add the stems of these forms to the analyser 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. [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Grow_bilingual More instructions for this task here]...
|dup=10
+
|dup=20
 
|beginner=no
 
|beginner=no
 
}}
 
}}
Line 181: Line 181:
 
{{Taskidea
 
{{Taskidea
 
|type=quality
 
|type=quality
|mentors=fotonzade, JNW, ftyers, anakuz, xavivars, Mikel, shardulc, sevilay, Unhammer, khannatanmai, dolphingarlic, wei2912, marcriera
+
|mentors=fotonzade, JNW, ftyers, anakuz, xavivars, mlforcada, shardulc, sevilay, Unhammer, dolphingarlic, wei2912, marcriera
 
|tags=xml, dictionaries
 
|tags=xml, dictionaries
 
|title=Post-edit 500 sentences of any public domain text from %AAA% to %BBB%
 
|title=Post-edit 500 sentences of any public domain text from %AAA% to %BBB%
|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 from %AAA% to %BBB% using any available machine translation system and clean up the translations yourself manually. Commit the post-edited texts (in plain text format) to an existing (via pull request) or if needed new github repository for the pair in dev/ or texts/ folder. The texts are subject to mentor approval.
+
|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 from %AAA% to %BBB% using any available machine translation system and clean up the translations yourself manually. Commit the post-edited texts (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.
 
|multi=10
 
|multi=10
 
|beginner=yes
 
|beginner=yes
Line 191: Line 191:
 
{{Taskidea
 
{{Taskidea
 
|type=quality
 
|type=quality
|mentors=Mikel, anakuz, xavivars, fotonzade, sevilay, khannatanmai, dolphingarlic, wei2912, marcriera, padth4i
+
|mentors=mlforcada, anakuz, xavivars, fotonzade, sevilay, dolphingarlic, wei2912, marcriera, padth4i
 
|tags=disambiguation
 
|tags=disambiguation
 
|title=Disambiguate 500 tokens of text in %AAA%
 
|title=Disambiguate 500 tokens of text in %AAA%
Line 200: Line 200:
 
{{Taskidea
 
{{Taskidea
 
|type=research
 
|type=research
|mentors=eirien, khannatanmai, anakuz, marcriera, padth4i
+
|mentors=eirien, anakuz, marcriera, padth4i
 
|tags=dictionaries
 
|tags=dictionaries
 
|title=Categorise 100 words from frequency list in %AAA%
 
|title=Categorise 100 words from frequency list in %AAA%
Line 210: Line 210:
 
{{Taskidea
 
{{Taskidea
 
|type=research
 
|type=research
|mentors=eirien, anakuz, sevilay. marcriera
+
|mentors=eirien, anakuz, sevilay, marcriera
 
|tags=dictionaries
 
|tags=dictionaries
 
|title=Categorise 500 words from frequency list in %AAA%
 
|title=Categorise 500 words from frequency list in %AAA%
Line 222: Line 222:
 
|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 (?) [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Evaluation_of_translation_of_an_existing_pair Read more]...
+
|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 238: Line 238:
 
|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 255: Line 255:
 
|tags=python, irc
 
|tags=python, irc
 
|beginner=yes
 
|beginner=yes
|mentors=JNW
+
|mentors=JNW, popcorndude
 
}}
 
}}
   
Line 264: Line 264:
 
|tags=python, irc, wiki
 
|tags=python, irc, wiki
 
|beginner=yes
 
|beginner=yes
|mentors=JNW
+
|mentors=JNW, popcorndude
 
}}
 
}}
   
Line 277: Line 277:
 
{{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 286: Line 286:
 
{{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 295: Line 295:
 
|type=documentation
 
|type=documentation
 
|title=document usage of the apertium-separable module
 
|title=document usage of the apertium-separable module
|mentors=JNW
+
|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=C++, transducers, lsx
+
|tags=lsx, dictionaries, wiki
 
}}
 
}}
   
Line 303: Line 303:
 
|type=quality
 
|type=quality
 
|title=Beta-test the apertium-separable module
 
|title=Beta-test the apertium-separable module
|mentors=JNW, ftyers, wei2912
+
|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=C++, transducers, lsx
+
|tags=lsx, dictionaries
 
|multi=yes
 
|multi=yes
|dup=yes
+
|dup=20
 
}}
 
}}
   
Line 330: Line 330:
 
{{Taskidea
 
{{Taskidea
 
|type=code, design
 
|type=code, design
|mentors=JNW, jjjppp, sushain
+
|mentors=JNW, jjjppp, sushain, dolphingarlic
 
|tags=d3, javascript
 
|tags=d3, javascript
 
|title=Integrate globe viewer into language family visualiser interface
 
|title=Integrate globe viewer into language family visualiser interface
Line 337: Line 337:
 
|beginner=no
 
|beginner=no
 
}}
 
}}
  +
  +
{{Taskidea
  +
|type=code
  +
|mentors=JNW, jjjppp, dolphingarlic
  +
|tags=d3, javascript
  +
|title=Change hard-coded values to dynamic in the globe viewer's code
  +
|description=The [https://github.com/jonorthwash/Apertium-Global-PairViewer globe viewer] provides a globe visualisation of languages that we can translate a given language to and from. This task is to clean up its source code by changing hard-coded values (e.g. scales and object sizes) to dynamic values so that the code will be easier to maintain in the future. There is an [https://github.com/jonorthwash/Apertium-Global-PairViewer/issues/24 associated GitHub issue].
  +
|multi=no
  +
|beginner=no
  +
}}
  +
  +
{{Taskidea
  +
|type=code
  +
|mentors=JNW, jjjppp, dolphingarlic
  +
|tags=d3, javascript
  +
|title=Fix fading for flyers in globe viewer
  +
|description=The [https://github.com/jonorthwash/Apertium-Global-PairViewer globe viewer] provides a globe visualisation of languages that we can translate a given language to and from. Currently, the flyers, which are the 3D colored connections, fade as either end of the connection goes out of the current scope of the globe. However, this causes flyers that connect two far away languages to be invisible (see issue for example). This task is to change the current fading function to account for far away connections and allow them to stay visible. There is an [https://github.com/jonorthwash/Apertium-Global-PairViewer/issues/22 associated GitHub issue].
  +
|multi=no
  +
|beginner=yes
  +
}}
  +
  +
{{Taskidea
  +
|type=design
  +
|mentors=JNW, ftyers
  +
|tags=UD, design, svg
  +
|title=Design a logo for UD Annotatrix
  +
|description=UD Annotatrix needs a better logo, or set of logos. Have a look at the [https://github.com/jonorthwash/ud-annotatrix/tree/master/server/public current logos] and [https://jonorthwash.github.io/ud-annotatrix/ see them in use]. Design a potential replacement logo that meets the following requirements: somehow incorporates what UD Annotatrix is / is for, is not "cluttered" (like the current cat logo), and can be used at different sizes.
  +
|multi=yes
  +
|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 343: Line 440:
   
 
These are languages that can be substituted for AAA and/or BBB for tasks each mentor is listed to mentor above.
 
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.
   
 
{|class=wikitable
 
{|class=wikitable
Line 357: Line 456:
 
| xavivars || cat, spa, eng, fra
 
| xavivars || cat, spa, eng, fra
 
|-
 
|-
| unhammer || nno, nob, swe, dan, fao, sme, ovd
+
| Unhammer || nno, nob, swe, dan, fao, sme, ovd
 
|-
 
|-
 
| shardulc || eng, fra, mar, hin, urd, kan
 
| shardulc || eng, fra, mar, hin, urd, kan
Line 363: Line 462:
 
| 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
Line 382: Line 481:
 
|-
 
|-
 
| Oguz|| eng, tur, uig, aze, crh
 
| Oguz|| eng, tur, uig, aze, crh
  +
|-
  +
| mlforcada || eng, cat, eus, fra, por, glg, spa, gle, bre
  +
|-
  +
| ayushjain || eng, hin
  +
|-
  +
| jjjppp || eng, lat
 
|}
 
|}
   

Latest revision as of 07: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:

  1. 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.

[edit] Task ideas

The current task ideas here are for 2019. See Talk:Task ideas for Google Code-in for task ideas from previous years.

[edit] Mentors

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

[edit] Counts

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
Personal tools