Difference between revisions of "Google Code In 2017 Tasks"
Jump to navigation
Jump to search
(→Project Tasks: add mention of moved tasks) |
|||
| Line 42: | Line 42: | ||
= Project Tasks = | = Project Tasks = | ||
| − | + | * moved to private document on 2017-10-26 | |
[[Category:Google Code In]] | [[Category:Google Code In]] | ||
Revision as of 13:29, 1 November 2017
@ 
Interested Mentors
Please first fill out the Google form mentioned at the top of: Google Code In 2017 Mentors
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
Beginner Tasks
- A student can only complete a total of 2 beginner tasks
- Each OSGeo project should specify that a task is a beginner task by including "[BEGINNER]" at the end of the task name
Example Tasks
- Haiku project's 2016 tasks: https://codein.withgoogle.com/archive/2016/organization/5146925732986880/task/
- Haiku project's tasks in json format: https://raw.githubusercontent.com/pulkomandy/GCITool/master/tasks.json
- "Install and open project XXX and take a screenshot showing the interface, with your Code-in dashboard in the background"
- "Fix an issue in the tracker for project XXX [DIFFICULT]"
- "Present the project XXX to your class [BEGINNER]"
Project Tasks
- moved to private document on 2017-10-26