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

From Apertium
Jump to navigation Jump to search
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 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 93: Line 93:
 
{{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 103: Line 103:
 
{{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 113: Line 113:
 
{{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 248: Line 248:
 
|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 265: Line 265:
 
|tags=python, irc
 
|tags=python, irc
 
|beginner=yes
 
|beginner=yes
|mentors=JNW
+
|mentors=JNW, popcorndude
 
}}
 
}}
   
Line 274: Line 274:
 
|tags=python, irc, wiki
 
|tags=python, irc, wiki
 
|beginner=yes
 
|beginner=yes
|mentors=JNW
+
|mentors=JNW, popcorndude
 
}}
 
}}
   
Line 287: Line 287:
 
{{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 296: Line 296:
 
{{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 305: Line 305:
 
|type=documentation
 
|type=documentation
 
|title=document usage of the apertium-separable module
 
|title=document usage of the apertium-separable module
|mentors=JNW, khannatanmai
+
|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=lsx, dictionaries, wiki
 
|tags=lsx, dictionaries, wiki
Line 313: Line 313:
 
|type=quality
 
|type=quality
 
|title=Beta-test the apertium-separable module
 
|title=Beta-test the apertium-separable module
|mentors=JNW, ftyers, wei2912, khannatanmai, dolphingarlic
+
|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=lsx, dictionaries
 
|tags=lsx, dictionaries
Line 405: Line 405:
 
| 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

Revision as of 20:51, 25 November 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

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

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

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