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

From Apertium
Jump to navigation Jump to search
m (Task addition for Apertium+Python)
Line 548: Line 548:
 
|-
  
|-
 
|{{sc|code}}
  
|{{sc|code}}
−
|align="right"|34
 +
|align="right"|35
 
|-
  
|-
 
|{{sc|documentation}}
  
|{{sc|documentation}}
Line 563: Line 563:
 
|- class="sortbottom"
  
|- class="sortbottom"
 
!Total
  
!Total
−
|align="right"|52
 +
|align="right"|53
 
|}
  
|}
   

Revision as of 20:23, 21 September 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=67664"