Difference between revisions of "Task ideas for Google Code-in"

From Apertium
Jump to navigation Jump to search
 
(282 intermediate revisions by 28 users not shown)
Line 1: Line 1:
  +
 
{{TOCD}}
 
{{TOCD}}
 
This is the task ideas page for [https://developers.google.com/open-source/gci/ 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.
 
This is the task ideas page for [https://developers.google.com/open-source/gci/ 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.
Line 4: Line 5:
 
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:
 
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 does not include time taken to [[Minimal installation from SVN|install]] / set up apertium'''.
+
<!--# '''this does not include time taken to [[Minimal installation from SVN|install]] / set up apertium (and relevant tools)'''.-->
 
# 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.
 
# 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.
   
Line 14: Line 15:
 
* {{sc|research}}: Tasks related to community management, outreach/marketting, or studying problems and recommending solutions
 
* {{sc|research}}: Tasks related to community management, outreach/marketting, or studying problems and recommending solutions
 
* {{sc|quality}}: Tasks related to testing and ensuring code is of high quality.
 
* {{sc|quality}}: Tasks related to testing and ensuring code is of high quality.
* {{sc|interface}}: Tasks related to user experience research or user interface design and interaction
+
* {{sc|design}}: Tasks related to user experience research or user interface design and interaction
   
 
'''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
   
You can find descriptions of some of the mentors here: [[List_of_Apertium_mentors]].
+
You can find descriptions of some of the mentors [[List_of_Apertium_mentors | here]].
   
==Task ideas==
+
== Task ideas ==
  +
<table class="sortable wikitable">
 
  +
'''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" 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>
  +
{{Taskidea|type=interface|mentors=Fran, Masha|tags=annotation, annotatrix
 
  +
{{Taskidea
|title=Nicely laid out interface for ud-annotatrix
 
  +
|type=research, quality, documentation
|description=Design an HTML layout for the annotatrix tool that makes best use of the space and functions nicely
 
  +
|title=Adopt a Wiki page
at different screen resolutions.
 
  +
|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=interface|mentors=Fran, Masha|tags=annotation, annotatrix
 
  +
{{Taskidea
|title=Come up with a CSS style for annotatrix
 
  +
|type=research, quality, documentation
|description=
 
  +
|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
  +
|mentors=*
  +
|multi=150
  +
|beginner=yes
 
}}
 
}}
  +
{{Taskidea|type=code|mentors=Fran, Masha|tags=annotation, annotatrix
 
  +
{{Taskidea
|title=SDparse to CoNLL-U converter in JavaScript
 
  +
|type=research, code
|description=SDparse is a format for describing dependency trees, they look like relation(head, dependency). CoNLL-U is another
 
  +
|title=expand coverage of Kyrgyz to English structural transfer
format for describing dependency trees. Make a converter between the two formats. The GitHub issue is [https://github.com/jonorthwash/ud-annotatrix/issues/88 here].
 
  +
|description=Find a sentence in Kyrgyz that once the lexical items are added to the bilingual dictionary is not fully (or correctly) parsed by the <tt>kir-eng-transfer</tt> Apertium mode. Determine what rule(s) need(s) to be added (or fixed) to cover this structure, and update <tt>apertium-eng-kir.kir-eng.rtx</tt> accordingly. You will first want to clone and compile [https://github.com/apertium/apertium-eng-kir apertium-eng-kir].
  +
|tags=Kyrgyz, English, recursive transfer, pairs
  +
|mentors=JNW, popcorndude
  +
|multi=150
  +
|dup=10
 
}}
 
}}
  +
{{Taskidea|type=quality|mentors=Fran, Masha|tags=annotation, annotatrix
 
  +
{{Taskidea
|title=Write a test for the format converters in annotatrix
 
  +
|type=code
|description=
 
  +
|title=Add recursive transfer support to a language pair that doesn't support it
|multi=yes
 
  +
|description=Make a branch of an Apertium language pair that doesn't support recursive transfer and call it "recursive transfer". Add vanilla <tt>.rtx</tt> files for both directions, and modify <tt>Makefile.am</tt> and <tt>modes.xml</tt> so that the branch compiles and runs. See [http://wiki.apertium.org/wiki/Apertium-recursive#Incorporating_Into_a_Pair this page] for instructions on how to do this.
  +
|tags=recursive transfer, pairs
  +
|mentors=JNW, popcorndude
  +
|multi=150
  +
|dup=10
  +
|beginner=yes
 
}}
 
}}
  +
{{Taskidea|type=code|mentors=Fran, Masha|tags=annotation, annotatrix
 
  +
{{Taskidea
|title=Write a function to detect invalid trees in annotatrix and advise the user
 
  +
|type=code
|description=It is possible to detect invalid trees (such as those that have cycles). We would like to write a function to detect those kinds of trees and advise the user. The GitHub issue is [https://github.com/jonorthwash/ud-annotatrix/issues/96 here].
 
  +
|title=Add 2 recursive transfer rules to a language pair
  +
|description=Add two recursive transfer rules to an Apertium language pair. These rules consist of, at minimum, a syntactic pattern to match, a phrase to combine them into, and an output pattern ([http://wiki.apertium.org/wiki/Apertium-recursive#Further_Documentation more documentation here]). If the language pair does not support recursive transfer, make sure [http://wiki.apertium.org/wiki/Apertium-recursive#Incorporating_Into_a_Pair to set it up] first. Submit your work as a pull request to a new branch ("recursive", "rtx", or similar) of the repository on GitHub.
  +
|tags=recursive transfer, pairs
  +
|mentors=JNW, popcorndude
  +
|multi=150
  +
|dup=20
 
}}
 
}}
  +
{{Taskidea|type=documentation|mentors=Fran, Masha|tags=annotation, annotatrix
 
  +
{{Taskidea
|title=Write a tutorial on how to use annotatrix to annotate a dependency tree
 
  +
|type=code
|description=Give step by step instructions to annotating a dependency tree with Annotatrix. Make sure you include all possibilities in the app, for example tokenisation options.
 
  +
|mentors=JNW, wei2912, padth4i, popcorndude
  +
|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.
  +
|tags=languages, bootstrap, dictionaries, translators
  +
|beginner=yes
  +
|multi=25
 
}}
 
}}
  +
{{Taskidea|type=documentation|mentors=Fran, Masha|tags=annotation, annotatrix
 
  +
{{Taskidea
|title=Make a video tutorial to annotating a dependency tree with annotatrix
 
  +
|type=code
|description=Give step by step instructions to annotating a dependency tree with Annotatrix. Make sure you include all possibilities in the app, for example tokenisation options.
 
  +
|mentors=JNW, wei2912, padth4i, popcorndude
  +
|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...]]
  +
|tags=languages, bootstrap, dictionaries
  +
|beginner=yes
  +
|multi=25
 
}}
 
}}
  +
{{Taskidea|type=quality|mentors=Masha|tags=xml, dictionaries, svn
 
  +
{{Taskidea
|title=Merge two versions of the Polish morphological dictionary
 
  +
|type=code
|description=At some point in the past, someone deleted a lot of entries from the Polish morphological dictionary, and unfortunately we didn't notice at the time and have since added stuff to it. The objective of this task is to take the last
 
  +
|mentors=JNW, sevilay, Unhammer, marcriera, padth4i, Oguz, popcorndude
version before the mass deletion and the current version and merge them.
 
  +
|title=Write 10 lexical selection for an existing translation pair
Getting list of the changes:
 
  +
|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...]]
$ svn diff --old apertium-pol.pol.dix@73196 --new apertium-pol.pol.dix@73199 > changes.diff
 
  +
|tags=languages, bootstrap, lexical selection, translators
  +
|multi=25
  +
|dup=5
 
}}
 
}}
  +
{{Taskidea|type=quality|mentors=fotonzade,Jonathan
 
  +
{{Taskidea
|tags=xml, dictionaries, svn
 
  +
|type=code
|title=Add 200 new entries to a bidix to language pair %AAA%-%BBB%
 
  +
|mentors=JNW, Unhammer, padth4i, Oguz, popcorndude
|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.
 
  +
|title=Write 10 constraint grammar rules for an existing language module
|multi=yes
 
  +
|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...]]
|bgnr=yes
 
  +
|tags=languages, bootstrap, constraint grammar
  +
|multi=25
  +
|dup=5
 
}}
 
}}
  +
{{Taskidea|type=quality|mentors=fotonzade,Jonathan
 
  +
{{Taskidea
|tags=xml, dictionaries, svn
 
  +
|type=research
|title=Add 500 new entries to a bidix to language pair %AAA%-%BBB%
 
  +
|mentors=anakuz, fotonzade
|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.
 
  +
|title=Syntactic annotation of text
|multi=yes
 
  +
|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.
  +
|tags=UD, trees, annotation
 
}}
 
}}
  +
{{Taskidea|type=quality|mentors=fotonzade|tags=disambiguation, svn
 
  +
{{Taskidea
|title=Disambiguate 500 tokens of text in %AAA%
 
  +
|type=research
|description=Run some text through a morphological analyser and disambiguate the output. Contact the mentor beforehand to approve the choice of language and text.
 
  +
|mentors=JNW,ftyers, fotonzade, anakuz, Oguz
|multi=yes
 
  +
|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.
  +
|tags=morphology, ud, dependencies
  +
|beginner=
  +
|multi=5
 
}}
 
}}
  +
{{Taskidea|type=code|mentors=Fran, Katya|tags=morphology, languages, finite-state, fst
 
  +
{{Taskidea
|title=Use apertium-init to start a new morphological analyser for %AAA%
 
  +
|type=research
|description=Use apertium-init to start a new morphological analyser (for a language we don't already
 
  +
|mentors=JNW, ftyers, fotonzade, anakuz
have, e.g. %AAA%) and add 100 words.
 
  +
|title=Create an Apertium-UD morphology mapping
|multi=yes
 
  +
|description=Choose a language that has an Apertium morphological analyser and adapt it to convert the morphology to UD morphology
  +
|tags=morphology, ud, dependencies
  +
|beginner=
  +
|multi=5
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=documentation
+
|type=quality
  +
|title=Install Apertium and verify that it works
|mentors=Jonathan
 
  +
|description=See [[Installation]] for instructions and if you encounter any issues along the way, document them and/or improve the wiki instructions!
|title=add comments to .dix file symbol definitions
 
|tags=dix
+
|tags=bash
  +
|mentors=ftyers, JNW, Unhammer, anakuz, Josh, fotonzade, sevilay, eirien, wei2912, padth4i, jjjppp
  +
|multi=150
  +
|beginner=yes
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=documentation
+
|type=research
  +
|title=Write a contrastive grammar
|mentors=Jonathan
 
  +
|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.
|title=find symbols that aren't on the list of symbols page
 
  +
|mentors=mlforcada, JNW, Josh, xavivars, fotonzade, sevilay, khannatanmai, dolphingarlic, padth4i
|description=Go through symbol definitions in Apertium dictionaries in svn (.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.
 
|tags=wiki,lexc,dix
+
|tags=wiki, languages
  +
|beginner=yes
  +
|multi=40
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code
+
|type=quality
  +
|mentors=mlforcada, anakuz, xavivars, fotonzade, sevilay, Unhammer, eirien, dolphingarlic, wei2912, marcriera, padth4i, Oguz, JNW, jjjppp
|title=conllu parser and searching
 
  +
|tags=xml, dictionaries
|description=Write a script (preferably in python3) that will parse files in conllu format, and perform basic searches, such as "find a node that has an nsubj relation to another node that has a noun POS" or "find all nodes with a cop label and a past feature"
 
  +
|title=Identify and add 100 new entries to the bilingual dictionary for the %AAA%-%BBB% language pair
|tags=python,dependencies
 
  +
|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]...
|mentors=Jonathan, Fran, Wei En
 
  +
|multi=40
  +
|beginner=yes
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code
+
|type=quality
  +
|mentors=mlforcada, anakuz, xavivars, fotonzade, ftyers, sevilay, eirien, dolphingarlic, wei2912, marcriera, padth4i, Oguz, JNW
|title=group and count possible lemmas output by guesser
 
  +
|tags=xml, dictionaries
|mentors=Jonathan, Fran, Wei En
 
  +
|title=Identify and add 250 new entries to the bilingual dictionary for the %AAA%-%BBB% language pair
|description=Currently a "guesser" version of Apertium transducers can output a list of possible analyses for unknown forms. Develop a new pipleine, preferably with shell scripts or python, that uses a guesser on all unknown forms in a corpus, and takes the list of all possible analyses, and output a hit count of the most common combinations of lemma and POS tag.
 
  +
|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]...
|tags=guesser,transducers,shellscripts
 
  +
|dup=20
  +
|beginner=no
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code
+
|type=quality
  +
|mentors=fotonzade, JNW, ftyers, anakuz, xavivars, mlforcada, shardulc, sevilay, Unhammer, dolphingarlic, wei2912, marcriera
|title=vim mode/tools for annotating dependency corpora in CG3 format
 
  +
|tags=xml, dictionaries
|mentors=Jonathan, Fran
 
  +
|title=Post-edit 500 sentences of any public domain text from %AAA% to %BBB%
|description=includes formatting, syntax highlighting, navigation, adding/removing nodes, updating node numbers, etc.
 
  +
|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.
|tags=vim,dependencies,CG3
 
  +
|multi=10
  +
|beginner=yes
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code
+
|type=quality
  +
|mentors=mlforcada, anakuz, xavivars, fotonzade, sevilay, dolphingarlic, wei2912, marcriera, padth4i
|title=vim mode/tools for annotating dependency corpora in CoNLL-U format
 
  +
|tags=disambiguation
|mentors=Jonathan, Fran
 
  +
|title=Disambiguate 500 tokens of text in %AAA%
|description=includes formatting, syntax highlighting, navigation, adding/removing nodes, updating node numbers, etc.
 
  +
|description=Run some text through a morphological analyser and disambiguate the output. Discuss with the mentor beforehand to approve the choice of language and text. [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Manually_disambiguate_text Read more]...
|tags=vim,dependencies,conllu
 
  +
|multi=yes
}}{{Taskidea
 
|type=quality
 
|title=figure out one-to-many bug in the [[lsx module]]
 
|mentors=Jonathan, Fran, Wei En
 
|description=
 
|tags=C++,transducers,lsx
 
}}{{Taskidea
 
|type=code
 
|title=add an option for reverse compiling to the [[lsx module]]
 
|mentors=Jonathan, Fran, Wei En
 
|description=this should be simple as it can just leverage the existing lttoolbox options for left-right / right-left compiling
 
|tags=C++,transducers,lsx
 
}}{{Taskidea
 
|type=quality
 
|title=remove extraneous functions from lsx-comp and clean up the code
 
|mentors=Jonathan, Fran, Wei En
 
|description=
 
|tags=C++,transducers,lsx
 
}}{{Taskidea
 
|type=quality
 
|title=remove extraneous functions from lsx-proc and clean up the code
 
|mentors=Jonathan, Fran, Wei En
 
|description=
 
|tags=C++,transducers,lsx
 
}}{{Taskidea
 
|type=code
 
|title=script to test coverage over wikipedia corpus
 
|mentors=Jonathan, Wei En
 
|description=Write a script (in python or ruby) that in one mode checks out a specified language module to a given directory, compiles it (or updates it if already existant), and then gets the most recently nightly wikipedia archive for that language and runs coverage over it (as much in RAM if possible). In another mode, it compiles the language pair in a docker instance that it then disposes of after successfully running coverage. Scripts exist in Apertium already for finding where a wikipedia is, extracting a wikipedia archive into a text file, and running coverage.
 
|tags=python,ruby,wikipedia
 
}}{{Taskidea
 
|type=quality,code
 
|title=fix any open ticket
 
|description=Fix any open ticket in any of our issues trackers: [https://sourceforge.net/p/apertium/tickets/ main], [https://github.com/goavki/apertium-html-tools/issues html-tools], [https://github.com/goavki/phenny/issues begiak]. When you claim this task, let your mentor know which issue you plan to work on.
 
|mentors=Jonathan, Wei En, Sushain
 
|multi=25
 
|dup=10
 
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=quality,code
+
|type=research
  +
|mentors=eirien, anakuz, marcriera, padth4i
|title=make html-tools do better on Chrome's audit
 
  +
|tags=dictionaries
|tags=javascript,html,css,web
 
  +
|title=Categorise 100 words from frequency list in %AAA%
|description=Currently, apertium.org and generally any [https://github.com/goavki/apertium-html-tools html-tools] installation fails lots of Chrome audit tests. As many as possible should be fixed. Ones that require substantial work should be filed as tickets and measures should be taken to prevent problems from reappearing (e.g. a test or linter rule). More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/201 #201]) and asynchronous discussion should occur there.
 
  +
|description=Categorise words by frequency into one of the major part-of-speech categories. You will receive a frequency list. Work from top to bottom. At the beginning of each line you should put a letter which categorises the word form by its part-of-speech. For example n for noun, v for verb, etc. [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Categorise_words_from_frequency_list Read more]... <!-- Wouldn't it be better for them to to add directly to the analyser? Easier for us, and more educational for them! -JNW -->
|mentors=Jonathan, Sushain
 
  +
|multi=yes
  +
|beginner=yes
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,interface
+
|type=research
  +
|mentors=eirien, anakuz, sevilay, marcriera
|title=upgrade html-tools to Bootstrap 4
 
  +
|tags=dictionaries
|tags=javascript,html,css,web
 
  +
|title=Categorise 500 words from frequency list in %AAA%
|description=Currently, [https://github.com/goavki/apertium-html-tools html-tools] uses Bootstrap 3.x. Bootstrap 4 beta is out and we can upgrade (hopefully)! If an upgrade is not possible, you should document why it's not and ensure that it's easy to upgrade when the blockers are removed. More information may be available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/200 #200]) and asynchronous discussion should occur there.
 
  +
|description=Categorise words by frequency into one of the major part-of-speech categories. You will receive a frequency list. Work from top to bottom. At the beginning of each line you should put a letter which categorises the word form by its part-of-speech. For example n for noun, v for verb, etc. [http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/Categorise_words_from_frequency_list Read more]... <!-- Wouldn't it be better for them to to add directly to the analyser? Easier for us, and more educational for them! -JNW -->
|mentors=Sushain
 
|bgnr=yes
+
|multi=yes
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,interface
+
|type=research
  +
|mentors=khannatanmai, sevilay, padth4i
|title=display API endpoint on sandbox
 
  +
|tags=evaluation
|tags=javascript,html,css,web
 
  +
|title=Evaluate an existing apertium pair %AAA% to %BBB% on a text
|description=Currently, [https://github.com/goavki/apertium-html-tools html-tools] has an "APy" mode where users can easily test out the API. However, it doesn't display the actual URL of the API endpoint and it would be nice to show that to the user. More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/147 #147]) and asynchronous discussion should occur there.
 
  +
|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]...
|mentors=Sushain, Jonathan
 
|bgnr=yes
 
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,quality,research
+
|type=code, research
  +
|title=Add apertium-anaphora support to a new language pair
|title=set up a testing framework for html-tools
 
  +
|description=Make a branch of an Apertium language pair that doesn't use apertium-anaphora yet, and call it "anaphora". Manually add the correct antecedent to side ref of the anaphors in the output of biltrans, and modify t1x to change the anaphor based on its antecedent. Verify that it runs and gives the correct anaphor. See the [http://wiki.apertium.org/wiki/Anaphora_Resolution_Module documentation] of the apertium-anaphora module for help.
|tags=javascript,html,css,web
 
  +
|tags=apertium-anaphora, transfer
|description=Currently, [https://github.com/goavki/apertium-html-tools html-tools] has no tests (sad!). This task requires researching what solutions there are for testing jQuery based web applications and putting one into place with a couple tests as a proof of concept. More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/116 #116]) and asynchronous discussion should occur there.
 
|mentors=Sushain
+
|mentors=khannatanmai
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,research
+
|type=code, research
  +
|title=Add one markable to the arx file for a language pair
|title=make html-tools automatically download translated files in Safari, IE, etc.
 
  +
|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=javascript,html,css,web
 
  +
|tags=apertium-anaphora, anaphora resolution
|description=Currently, [https://github.com/goavki/apertium-html-tools html-tools] is capable of translating files. However, this translation does not always result in the file immediately being download to the user on all browsers. It would be awesome if it did! This task requires researching what solutions there are, evaluating them against each other and it may result in a conclusion that it just isn't possible (yet). More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/97 #97]) and asynchronous discussion should occur there.
 
|mentors=Sushain, Jonathan, Unhammer
+
|mentors=khannatanmai, popcorndude
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,interface
+
|type=code
  +
|title=Write a TextMate grammar for CG-3 syntax highlighting
|title=make html-tools properly align text in mixed RTL/LTR contexts
 
  +
|description=We want CG-3 files to be syntax highlighted in Github. They use TextMate-compatible grammars. See [https://github.com/TinoDidriksen/cg3/issues/48 issue 48] in the CG-3 repo.
|tags=javascript,html,css,web
 
  +
|tags=cg, editors, tools
|description=Currently, [https://github.com/goavki/apertium-html-tools html-tools] is capable of displaying results/allowing input for RTL languages in a LTR context (e.g. we're translating Arabic in an English website). However, this doesn't always look exactly how it should look, i.e. things are not aligned correctly. More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/49 #49]) and asynchronous discussion should occur there.
 
|mentors=Sushain, Jonathan
+
|mentors=Unhammer
|bgnr=yes
 
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,interface
+
|type=code
  +
|title=Make Apertium IRC bot's messaging system case-insensitive
|title=de-conflict the 'make a suggestion' interface in html-tools
 
  +
|description=[[Begiak]] is Apertium's IRC bot. It has a messaging system, where you can say e.g. "begiak, tell randomuser thanks for the tip!" or "begiak: ask randomuser where they filed that issue", and the bot will deliver the message next time it sees randomuser say something. There's been [https://github.com/apertium/phenny/issues/488 a request] for begiak to recognise case-insensitive commands. Your job is to create a fix for this and submit a pull request to the repository with the fix.
|tags=javascript,html,css,web
 
  +
|tags=python, irc
|description=There has been much demand for [https://github.com/goavki/apertium-html-tools html-tools] to support an interface for users making suggestions regarding e.g. incorrect translations (c.g. Google translate). An interface was designed for this purpose. However, since it has been a while since anyone touched it, the code now conflicts with the current master branch. There are also some refinements that could be warranted. This task requires de-conflicting this [https://github.com/goavki/apertium-html-tools/pull/74 branch] with master, providing screenshots/demo videos of the interface for mentors and analysing how it can be improved (not carrying out these improvements, this would be a later task!). More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/74 #74]) and asynchronous discussion should occur there.
 
  +
|beginner=yes
|mentors=Sushain, Jonathan
 
  +
|mentors=JNW, popcorndude
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=quality,code
+
|type=code
  +
|title=Make Apertium's IRC bot's updating of Apertium's wiki format numbers better
|title=make html-tools do better on Chrome's audit
 
  +
|description=[[Begiak]] is Apertium's IRC bot. It has a module that allows users on IRC to trigger a script that updates the Apertium wiki with statistics about Apertium modules. There have been [https://github.com/apertium/phenny/issues/485 complaints about the formatting of the numbers it writes]. Your job is to create a fix for this and submit a pull request to the repository with the fix.
|tags=javascript,html,css,web
 
  +
|tags=python, irc, wiki
|description=Currently, apertium.org and generally any [https://github.com/goavki/apertium-html-tools html-tools] installation fails lots of Chrome audit tests. As many as possible should be fixed. Ones that require substantial work should be filed as tickets and measures should be taken to prevent problems from reappearing (e.g. a test or linter rule). More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/201 #201]) and asynchronous discussion should occur there.
 
  +
|beginner=yes
|mentors=Jonathan, Sushain
 
  +
|mentors=JNW, popcorndude
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,interface
+
|type=code
  +
|title=Create a new init script for Apertium's IRC bot
|title=upgrade html-tools to Bootstrap 4
 
  +
|description=[[Begiak]] is Apertium IRC bot. It runs on a low-power server that runs Debian. Sometimes that server is reset, and we have to manually restart begiak. The init script that used to control begiak no longer seems to work. Your task is to create a new init script that supports the normal sort of actions that init scripts do, and also the following options for begiak: the specific path to run it from, the user to run it as, miscellaneous arguments, and a log file to log its output. This init script should live in the repository in a reasonable place. There is a [https://github.com/apertium/phenny/issues/484 github issue describing this task].
|tags=javascript,html,css,web
 
  +
|tags=python, debian, init, irc
|description=Currently, [https://github.com/goavki/apertium-html-tools html-tools] uses Bootstrap 3.x. Bootstrap 4 beta is out and we can upgrade (hopefully)! If an upgrade is not possible, you should document why it's not and ensure that it's easy to upgrade when the blockers are removed. More information may be available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/200 #200]) and asynchronous discussion should occur there.
 
|mentors=Sushain
+
|mentors=JNW
|bgnr=yes
 
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,interface
+
|type=documentation
  +
|mentors=JNW, flammie, popcorndude
|title=display API endpoint on sandbox
 
  +
|title=Add comments to a dictionary defining the symbols used in it
|tags=javascript,html,css,web
 
  +
|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=Currently, [https://github.com/goavki/apertium-html-tools html-tools] has an "APy" mode where users can easily test out the API. However, it doesn't display the actual URL of the API endpoint and it would be nice to show that to the user. More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/147 #147]) and asynchronous discussion should occur there.
 
  +
|tags=dictionaries
|mentors=Sushain, Jonathan
 
  +
|dup=10
|bgnr=yes
 
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,quality,research
+
|type=documentation
  +
|mentors=JNW, popcorndude
|title=set up a testing framework for html-tools
 
  +
|title=find symbols that aren't on the list of symbols page
|tags=javascript,html,css,web
 
  +
|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=Currently, [https://github.com/goavki/apertium-html-tools html-tools] has no tests (sad!). This task requires researching what solutions there are for testing jQuery based web applications and putting one into place with a couple tests as a proof of concept. More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/116 #116]) and asynchronous discussion should occur there.
 
  +
|tags=wiki,dictionaries
|mentors=Sushain
 
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,research
+
|type=documentation
  +
|title=document usage of the apertium-separable module
|title=make html-tools automatically download translated files in Safari, IE, etc.
 
  +
|mentors=JNW, khannatanmai, popcorndude
|tags=javascript,html,css,web
 
  +
|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=Currently, [https://github.com/goavki/apertium-html-tools html-tools] is capable of translating files. However, this translation does not always result in the file immediately being download to the user on all browsers. It would be awesome if it did! This task requires researching what solutions there are, evaluating them against each other and it may result in a conclusion that it just isn't possible (yet). More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/97 #97]) and asynchronous discussion should occur there.
 
  +
|tags=lsx, dictionaries, wiki
|mentors=Sushain, Jonathan, Unhammer
 
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,interface
+
|type=quality
  +
|title=Beta-test the apertium-separable module
|title=make html-tools properly align text in mixed RTL/LTR contexts
 
  +
|mentors=JNW, ftyers, wei2912, khannatanmai, dolphingarlic, popcorndude
|tags=javascript,html,css,web
 
  +
|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=Currently, [https://github.com/goavki/apertium-html-tools html-tools] is capable of displaying results/allowing input for RTL languages in a LTR context (e.g. we're translating Arabic in an English website). However, this doesn't always look exactly how it should look, i.e. things are not aligned correctly. More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/49 #49]) and asynchronous discussion should occur there.
 
  +
|tags=lsx, dictionaries
|mentors=Sushain, Jonathan
 
|bgnr=yes
+
|multi=yes
  +
|dup=20
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,interface
+
|type=code, quality
  +
|title=script to test coverage of analyser over corresponding wikipedia corpus
|title=de-conflict the 'make a suggestion' interface in html-tools
 
  +
|mentors=JNW, wei2912
|tags=javascript,html,css,web
 
  +
|description=Write a script (in python or ruby) that tests coverage of an Apertium analyser over the latest Wikipedia corpus in that language. One mode of this script should check out a specified language module to a given directory, compile it (or updates it if already existant), and then get the most recently Wikipedia nightly archive for that language and run coverage over it (as much in RAM if possible). In another mode, it should compile the language pair in a docker instance that it then disposes of after successfully running coverage. Scripts exist in Apertium already for finding where a Wikipedia is, extracting a Wikipedia archive into a text file, and running coverage. Ask a mentor for help finding these scripts.
|description=There has been much demand for [https://github.com/goavki/apertium-html-tools html-tools] to support an interface for users making suggestions regarding e.g. incorrect translations (c.g. Google translate). An interface was designed for this purpose. However, since it has been a while since anyone touched it, the code now conflicts with the current master branch. There are also some refinements that could be warranted. This task requires de-conflicting this [https://github.com/goavki/apertium-html-tools/pull/74 branch] with master, providing screenshots/demo videos of the interface for mentors and analysing how it can be improved (not carrying out these improvements, this would be a later task!). More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/74 #74]) and asynchronous discussion should occur there.
 
  +
|tags=python, ruby, wikipedia
|mentors=Sushain, Jonathan
 
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,quality
+
|type=code, design
  +
|title=Make source browser headings sticky at bottom of window
|title=make html-tools capable of translating itself
 
  +
|description=Make headings that are out of view (either below when at the top, or above when scrolled down) sticky on [https://apertium.github.io/apertium-on-github/source-browser.html Apertium source browser], so that it's clear what other headings exist. There is a [https://github.com/apertium/apertium-on-github/issues/22 github issue for this].
|tags=javascript,html,css,web
 
  +
|tags=css, javascript, html, web
|description=Currently, [https://github.com/goavki/apertium-html-tools html-tools] supports website translation. However, if asked to translate itself, weird things happen and the interface does not properly load. This task requires figuring out the root problem and correcting the fault. More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/203 #203]) and asynchronous discussion should occur there.
 
|mentors=Sushain, Jonathan
+
|mentors=sushain, JNW, xavivars
  +
|multi=
|bgnr=yes
 
  +
|beginner=no
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=code,quality,interface
+
|type=code, design
  +
|mentors=JNW, jjjppp, sushain, dolphingarlic
|title=make html-tools stop using inline styles
 
|tags=html,css,web
+
|tags=d3, javascript
  +
|title=Integrate globe viewer into language family visualiser interface
|description=Currently, [https://github.com/goavki/apertium-html-tools html-tools] has inline styles. These are not very maintainable and widely considered as bad style. This task requires surveying the uses, removing all of them in a clean manner, i.e. semantically, and re-enabling the linter rule that will prevent them going forward. More information is available in the issue tracker ([https://github.com/goavki/apertium-html-tools/issues/114 #114]) and asynchronous discussion should occur there.
 
  +
|description=The [https://github.com/apertium/family-visualizations family visualiser interface] has four info boxes when a language is clicked on, and one of those boxes is empty. 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 integrate the globe viewer for a specific language into the fourth box in the family visualiser. There is an [https://github.com/jonorthwash/Apertium-Global-PairViewer/issues/32 associated GitHub issue].
|mentors=Sushain
 
  +
|multi=no
|bgnr=yes
 
  +
|beginner=no
 
}}
 
}}
  +
 
{{Taskidea
 
{{Taskidea
|type=quality
+
|type=code
  +
|mentors=JNW, jjjppp, dolphingarlic
|title=find an apertium module not developed in svn and import it
 
  +
|tags=d3, javascript
|description=Find an Apertium module developed elsewhere (e.g., github) released under a compatible open license, and import it into [http://wiki.apertium.org/wiki/SVN Apertium's svn], being sure to attribute any authors (in an AUTHORS file) and keeping the original license. Once place to look for such modules might be among the [https://wikis.swarthmore.edu/ling073/Category:Sp17_FinalProjects final projects] in a recent Computational Linguistics course.
 
  +
|title=Change hard-coded values to dynamic in the globe viewer's code
|mentors=Jonathan, Wei En
 
  +
|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=10
 
  +
|multi=no
|dup=2
 
  +
|beginner=no
}}{{Taskidea
 
|type=code
 
|title=add an incubator mode to the wikipedia scraper
 
|tags=wikipedia,python
 
|description=Add a mode to scrape a Wikipedia in incubator (e.g,. [https://incubator.wikimedia.org/wiki/Wp/inh/Main_page the Ingush incubator]) to the [http://svn.code.sf.net/p/apertium/svn/trunk/apertium-tools/WikiExtractor.py WikiExtractor] script
 
|mentors=Jonathan, Wei En
 
}}{{Taskidea
 
|type=code,interface
 
|title=add a translation mode interface to the geriaoueg plugin for firefox
 
|description=Fork the [https://github.com/vigneshv59/geriaoueg-firefox geriaoueg firefox plugin] and add an interface for translation mode. It doesn't have to translate at this point, but it should communicate with the server (as it currently does) to load available languages.
 
|tags=javascript
 
|mentors=Jonathan
 
}}{{Taskidea
 
|type=code,interface
 
|title=add a translation mode interface to the geriaoueg plugin for chrome
 
|description=Fork the [https://github.com/vigneshv59/geriaoueg-chrome geriaoueg chrome plugin] and add an interface for translation mode. It doesn't have to translate at this point, but it should communicate with the server (as it currently does) to load available languages.
 
|tags=javascript
 
|mentors=Jonathan
 
 
}}
 
}}
  +
  +
{{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>
   
  +
==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.
  +
  +
{|class=wikitable
  +
! 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 ==
  +
  +
Last updated by [[User:Firespeaker|Firespeaker]] ([[User talk:Firespeaker|talk]]) 07:30, 28 October 2019 (CET).
  +
  +
{| class="sortable wikitable"
  +
|-
  +
! scope="col" | Category
  +
! scope="col" | Count
  +
|-
  +
|{{sc|code}}
  +
|align="right"|16
  +
|-
  +
|{{sc|documentation}}
  +
|align="right"|4
  +
|-
  +
|{{sc|research}}
  +
|align="right"|11
  +
|-
  +
|{{sc|quality}}
  +
|align="right"|8
  +
|-
  +
|{{sc|design}}
  +
|align="right"|2
  +
|- class="sortbottom"
  +
!Total
  +
|align="right"|33
  +
|}
   
 
[[Category:Google Code-in]]
 
[[Category:Google Code-in]]

Latest revision as of 06:23, 5 December 2019

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.

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