Task ideas for Google Code-in

From Apertium
Jump to: navigation, 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.

[edit] Task ideas

  • Fix a memory leak in matxin-transfer
  • Tag text in Apertium format
  • Convert Chukchi lexicon to HFST/lexc
    • Nouns
    • Numerals
    • Adjectives
  • 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
  • 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
  • convert UD treebank to apertium tags, use unigram tagger (see #apertium logs 2016-06-22)
  • convert http://youssefsan.eu/wiki/index.php?title=Wolof 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.
Personal tools