Difference between revisions of "Google Code In 2017 Tasks"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* Each task is expected to take '''3-5 hours''' of work to complete | * Each task is expected to take '''3-5 hours''' of work to complete | ||
* Students have at least '''3 days''' to complete the task | * Students have at least '''3 days''' to complete the task | ||
| + | |||
| + | = Types of Tasks = | ||
| + | |||
| + | There are 5 types of Code-in Tasks in general: | ||
| + | |||
| + | ;Code | ||
| + | : Tasks related to writing or refactoring code | ||
| + | ;Documentation/Training | ||
| + | : Tasks related to creating/editing documents and helping others learn more | ||
| + | ;Outreach/Research | ||
| + | : Tasks related to community management, outreach/marketing, or studying problems and recommending solutions | ||
| + | ;Quality Assurance | ||
| + | : Tasks related to testing and ensuring code is of high quality | ||
| + | ;User Interface | ||
| + | : Tasks related to user experience research or user interface design and interaction | ||
[[Category:Google Code In]] | [[Category:Google Code In]] | ||
Revision as of 15:45, 4 October 2017
@ 
Effort for a Task
- Each task is expected to take 3-5 hours of work to complete
- Students have at least 3 days to complete the task
Types of Tasks
There are 5 types of Code-in Tasks in general:
- Code
- Tasks related to writing or refactoring code
- Documentation/Training
- Tasks related to creating/editing documents and helping others learn more
- Outreach/Research
- Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
- Quality Assurance
- Tasks related to testing and ensuring code is of high quality
- User Interface
- Tasks related to user experience research or user interface design and interaction