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

From Apertium
Jump to navigation Jump to search
Line 282: Line 282:
|description=Currently, apertium-python requires a complex installation process for Windows (and Linux). The goal is something that works out-of-the-box with pip. See the associated [https://github.com/apertium/apertium-python/issues/6 GitHub issue] for more details and discussion.
|description=Currently, apertium-python requires a complex installation process for Windows (and Linux). The goal is something that works out-of-the-box with pip. See the associated [https://github.com/apertium/apertium-python/issues/6 GitHub issue] for more details and discussion.
|tags=python, windows
|tags=python, windows
|mentors=sushain, wei2912
|mentors=sushain, wei2912, arghya
|beginner=no
|beginner=no
}}
}}
Line 300: Line 300:
|description=Currently, there are some docstrings attached to functions and constants. This task requires setting up Sphinx/readthedocs for apertium-python so these docs are easily accessible. Types should also be visible and documentation should support being written in Markdown, not RST. See the associated [https://github.com/apertium/apertium-python/issues/4 GitHub issue] for more details and discussion.
|description=Currently, there are some docstrings attached to functions and constants. This task requires setting up Sphinx/readthedocs for apertium-python so these docs are easily accessible. Types should also be visible and documentation should support being written in Markdown, not RST. See the associated [https://github.com/apertium/apertium-python/issues/4 GitHub issue] for more details and discussion.
|tags=python, sphinx
|tags=python, sphinx
|mentors=sushain, Josh
|mentors=sushain, Josh, arghya
|beginner=no
|beginner=no
}}
}}

Revision as of 10:15, 19 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