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

From Apertium
Jump to navigation Jump to search
Line 53: Line 53:
|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].
|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=css, javascript, html, web
|tags=css, javascript, html, web
|mentors=sushain, JNW
|mentors=sushain, JNW, xavivars
|multi=
|multi=
|beginner=no
|beginner=no
Line 131: Line 131:
|description=Unfortunately, the transition to GitHub from SVN made it so this script which is very handy for downloading an Apertium language/pair doesn't fetch the newest packages anymore. This also means that beta.apertium.org is out of date. See the associated [https://github.com/apertium/apertium-get/issues/7 GitHub issue] issue for more details and discussion.
|description=Unfortunately, the transition to GitHub from SVN made it so this script which is very handy for downloading an Apertium language/pair doesn't fetch the newest packages anymore. This also means that beta.apertium.org is out of date. See the associated [https://github.com/apertium/apertium-get/issues/7 GitHub issue] issue for more details and discussion.
|tags=bash, github
|tags=bash, github
|mentors=sushain, Unhammer, wei2912, Josh
|mentors=sushain, Unhammer, wei2912, Josh, xavivars
|beginner=no
|beginner=no
}}
}}
Line 140: Line 140:
|description=Currently, some Apertium pairs/language modules use CI but it's very inconsistent and doesn't come by default. Apertium-init is the official way to bootstrap a new Apertium package so if it came with CI support by default, that would be great. See the associated [https://github.com/apertium/apertium-init/issues/51 GitHub issue] issue for more details and discussion.
|description=Currently, some Apertium pairs/language modules use CI but it's very inconsistent and doesn't come by default. Apertium-init is the official way to bootstrap a new Apertium package so if it came with CI support by default, that would be great. See the associated [https://github.com/apertium/apertium-init/issues/51 GitHub issue] issue for more details and discussion.
|tags=ci, circleci, yaml
|tags=ci, circleci, yaml
|mentors=sushain, Unhammer, wei2912
|mentors=sushain, Unhammer, wei2912, xavivars
|beginner=no
|beginner=no
}}
}}
Line 149: Line 149:
|description=Currently, some XML produced by [[Apertium-init]], a script which allows bootstrapping Apertium packages easily, has declarations and some doesn't. Moreover, the declarations are sometimes inconsistent. All XML files should have the same declaration. Note that not all of the XML files in [[Apertium-init]] use the .xml file extension. See the associated [https://github.com/apertium/apertium-init/issues/49 GitHub issue] issue for more details and discussion.
|description=Currently, some XML produced by [[Apertium-init]], a script which allows bootstrapping Apertium packages easily, has declarations and some doesn't. Moreover, the declarations are sometimes inconsistent. All XML files should have the same declaration. Note that not all of the XML files in [[Apertium-init]] use the .xml file extension. See the associated [https://github.com/apertium/apertium-init/issues/49 GitHub issue] issue for more details and discussion.
|tags=xml, python
|tags=xml, python
|mentors=sushain, Unhammer, wei2912
|mentors=sushain, Unhammer, wei2912, xavivars
|beginner=yes
|beginner=yes
}}
}}
Line 185: Line 185:
|description=[[Apertium-init]] bootstraps Apertium packages and supports creating an associated GitHub repository. Our source browser and other scripts expect a GitHub repository topic like "apertium-incubator". This task requires creating the incubator topic by default on repo push with an option for custom topics. See the associated [https://github.com/apertium/apertium-init/issues/36 GitHub issue] issue for more details and discussion.
|description=[[Apertium-init]] bootstraps Apertium packages and supports creating an associated GitHub repository. Our source browser and other scripts expect a GitHub repository topic like "apertium-incubator". This task requires creating the incubator topic by default on repo push with an option for custom topics. See the associated [https://github.com/apertium/apertium-init/issues/36 GitHub issue] issue for more details and discussion.
|tags=python, github, http
|tags=python, github, http
|mentors=sushain, Unhammer, wei2912
|mentors=sushain, Unhammer, wei2912, xavivars
|beginner=no
|beginner=no
}}
}}
Line 336: Line 336:
|description=Currently, language names that power part of the Apertium HTTP API are stored and updated in SQL. It would be nice if they were stored in a more human readable format like TSV and the SQLite were generated at build time. See the associated [https://github.com/apertium/apertium-apy/issues/115 GitHub issue] for more details and discussion.
|description=Currently, language names that power part of the Apertium HTTP API are stored and updated in SQL. It would be nice if they were stored in a more human readable format like TSV and the SQLite were generated at build time. See the associated [https://github.com/apertium/apertium-apy/issues/115 GitHub issue] for more details and discussion.
|tags=python, sql, tsv
|tags=python, sql, tsv
|mentors=sushain, Unhammer
|mentors=sushain, Unhammer, xavivars
|beginner=no
|beginner=no
}}
}}

Revision as of 17:16, 3 October 2018

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

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
Retrieved from "https://wiki.apertium.org/w/index.php?title=Task_ideas_for_Google_Code-in&oldid=67679"