Difference between revisions of "Google Code In 2017 Tasks"
Jump to navigation
Jump to search
| Line 102: | Line 102: | ||
=== MapGuide Open Source === | === MapGuide Open Source === | ||
| + | |||
| + | === MapProxy === | ||
=== MapServer === | === MapServer === | ||
Revision as of 10:25, 5 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
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 from Previous Years
- 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
Project Tasks
Choose tasks from any of the OSGeo projects below (these are official OSGeo projects, projects in OSGeo incubation, and OSGeo community projects):