Task ideas for Google Code-in

From Apertium
Revision as of 20:24, 27 October 2016 by Putti (talk | contribs) (Add couple task ideas)
Jump to navigation Jump to search


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 does not include time taken to install / set up apertium.
  2. 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.


  • 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.
  • interface: Tasks related to user experience research or user interface design and interaction

You can find descriptions of some of the mentors here: List_of_Apertium_mentors.

Task ideas

code Fix a memory leak in matxin-transfer hargle bargle
Fix a memory leak in matxin-transfer
Tag text in Apertium format
Convert Chukchi Nouns to HFST/lexc
Convert Chukchi Numerals to HFST/lexc
Convert Chukchi Adjectives to HFST/lexc
Make a (web) viewer for parallel treebanks (also for viewing diff annotation for same sentence)
Write a script to convert a UD treebank for a given language to a format suitable for training the perceptron tagger
Train the perceptron tagger for a language
Design an annotation tool for disambiguation
Design an annotation tool for adding dependencies
Train lexical selection rules from a large parallel corpus for a language pair
Document how to set up the experiments for weighted transfer rules
convert UD treebank to apertium tags, use unigram tagger (see #apertium logs 2016-06-22)
convert [1] to apertium-style documentation
implement `lt-print --strings` lt-print -s
Use d3 globe to make an apertium language/pair viewer (like pairviewer), maybe based on this or this or this.
make a thing to detect contexts where a path in a compiled transducer begins with a whitespace
make the lt-comp compiler print a warning when a path begins with a whitespace.
apertium-mar-hin: make the SL morph for any part of speech less daft
add other indic scripts/formal latin transliterations to the currently-just-WX transliterator
code refactor x file in apy Putti
documentation add docstrings to x file in apy Putti

  • apertium-hun:
    • hunmorph.db conversions
    • additional morphology
    • stuff
  • suggest a word feature to web translator:
    • user managements
    • saving data
    • deploy it to apertium.org? If it's already exisitng somewhere in githubs, maybe also to merge
    • merge Kira's contributions more generally
  • apertium-mar:
    • more consistency with apertium-hin for verbs
    • replace cases with postpositions
    • fix modals and quasi-modals
  • APYrtium CLARIN switchboard (oder Weblicht) compatabilitet:
    • make apy i/o into clarin compatible formats
    • make cmdi metadata of apertium (translators, analysers, etc.)
    • make parts of pipelines callable
  • apertium-fin-eng
    • sieve through the rubbish words and translations from finnwordnet (i.e. most of fin-eng bidix)
    • add words from eng side of the dix to apertium-eng
    • do stuff