Difference between revisions of "Google Code In 2017 Tasks"
Jump to navigation
Jump to search
Line 49: | Line 49: | ||
* Help and/or teach the student how to | * Help and/or teach the student how to | ||
** be a part of your community | ** be a part of your community | ||
− | communicate more effectively and in the open | + | ** communicate more effectively and in the open |
− | work with your org’s preferred communication channel (IRC, Slack, etc) | + | ** work with your org’s preferred communication channel (IRC, Slack, etc) |
− | use your org’s version control system | + | ** use your org’s version control system |
− | ask good questions and get answers to their questions | + | ** ask good questions and get answers to their questions |
− | provide convincing technical argument and constructive discussion | + | ** provide convincing technical argument and constructive discussion |
− | be independently motivated and productive | + | ** be independently motivated and productive |
− | solve difficult technical problems | + | ** solve difficult technical problems |
− | Keep track of their progress, keep student informed as to their status | + | * Keep track of their progress, keep student informed as to their status |
− | Communicate on a regular basis, once a week or better (for GSoC) | + | * Communicate on a regular basis, once a week or better (for GSoC) |
− | Give constructive feedback, be patient (particularly for GCI), and be respectful | + | ** Give constructive feedback, be patient (particularly for GCI), and be respectful |
− | Respond to questions within 24 hours (occasionally under 36 hours is ok) | + | ** Respond to questions within 24 hours (occasionally under 36 hours is ok) |
− | Establish realistic work objectives and timeline expectations | + | * Establish realistic work objectives and timeline expectations |
− | Re-evaluate scope with student when significantly ahead of or behind expectations | + | * Re-evaluate scope with student when significantly ahead of or behind expectations |
− | + | ** Give them extra time on a task as warranted | |
− | Work with devs and community to facilitate acceptance of student work | + | * Work with devs and community to facilitate acceptance of student work |
[[Category:Google Code In]] | [[Category:Google Code In]] |
Revision as of 05:27, 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
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
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
Mentor Responsibilities
...to OSGeo gci-admin team
- Communicate availability and interaction expectations
- Inform gci-admin team when mentoring capacity will be reduced, as early as possible (e.g., family, health, vacation)
- Inform gci-admin team when there is an issue with a student
- Lacking communication, activity, visibility (MIA), or progress
- Participant Agreement violations (e.g., plagiarism, harassment, fraud)
- Bad fit or stepping down
- Formally evaluate student participation
...to your Students
- Help and/or teach the student how to
- be a part of your community
- communicate more effectively and in the open
- work with your org’s preferred communication channel (IRC, Slack, etc)
- use your org’s version control system
- ask good questions and get answers to their questions
- provide convincing technical argument and constructive discussion
- be independently motivated and productive
- solve difficult technical problems
- Keep track of their progress, keep student informed as to their status
- Communicate on a regular basis, once a week or better (for GSoC)
- Give constructive feedback, be patient (particularly for GCI), and be respectful
- Respond to questions within 24 hours (occasionally under 36 hours is ok)
- Establish realistic work objectives and timeline expectations
- Re-evaluate scope with student when significantly ahead of or behind expectations
- Give them extra time on a task as warranted
- Work with devs and community to facilitate acceptance of student work