Task ideas for Google Code-in

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
• dup = number of times a student can do the same task

You can find descriptions of some of the mentors here.

Task ideas

See Talk:Task ideas for Google Code-in for task ideas from previous years.

type	title	description	tags	mentors	bgnr?	multi?	duplicates
research, quality	Adopt a Wiki page	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, and updating documentation to reflect the current options and defaults of various tools.	wiki	*	yes	40
research, code	expand coverage of Kyrgyz to English structural transfer	Find a sentence in Kyrgyz that once the lexical items are added to the bilingual dictionary is not fully (or correctly) parsed by the kir-eng-transfer Apertium mode. Determine what rule(s) need(s) to be added (or fixed) to cover this structure, and update apertium-eng-kir.kir-eng.rtx accordingly. You will first want to clone and compile apertium-eng-kir.	Kyrgyz, English, recursive transfer, pairs	JNW		20
code	Add recursive transfer support to a language pair that doesn't support it	Make a branch of an Apertium language pair that doesn't support recursive transfer and call it "recursive transfer". Add vanilla .rtx files for both directions, and modify Makefile.am and modes.xml so that the branch compiles and runs.	recursive transfer, pairs	JNW		20

Mentors

Mentor	Languages
ftyers	eng, spa, cat, fra, nor, rus, por, swe, tur, gag, aze
JNW	eng, spa, fra, rus, tur, gag, aze, kaz, kir, 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

Counts

Last updated by Sushain (talk) 19:22, 15 September 2018 (CEST).

Category	Count
code	35
documentation	5
research	10
quality	10
design	5
Total	53