| | 1 | = Google Code In 2014 = |
| | 2 | |
| | 3 | The Google Code-in is a programme to introduce pre-university students (ages 13-17) to the many kinds of contributions that make open source software development possible. Over the last four years there have been 1575 students from 78 countries that completed tasks in the online contest. It runs from December 1, 2014 to January 19, 2015. |
| | 4 | |
| | 5 | For many students the Google Code-in contest is their first introduction to open source development. The role of this page is to collect "bite sized" tasks on the Boost C++ Libraries for participating students to complete. Students gain real world experience working on an open source project and can put the skills they have been learning in the classroom to use in a open source project that can touch millions of lives. |
| | 6 | |
| | 7 | The tasks are grouped into the following categories: |
| | 8 | |
| | 9 | 1. Code: Tasks related to writing or refactoring code |
| | 10 | 2. Documentation or Training: Tasks related to creating/editing documents and helping others learn more |
| | 11 | 3. Outreach or Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions |
| | 12 | 4. Quality Assurance: Tasks related to testing and ensuring code is of high quality |
| | 13 | 5. User Interface: Tasks related to user experience research or user interface design and interaction |
| | 14 | |
| | 15 | Tasks generally take students 3-5 hours to complete. Students earn one point for each task completed. Students will receive a certificate for completing one task and can earn a tee shirt when they complete three tasks. At the end of the contest each of the open source organizations will name five (5) students as their finalists and these finalists will also earn a hooded sweatshirt. From their five (5) finalists, each organization will name two (2) grand prize winners for their organization based on the students' comprehensive body of work. The grand prize winners will receive a trip to Google's Mountain View, California, USA headquarters for themselves and a parent or legal guardian for an awards ceremony, an opportunity to meet with Google engineers, and have a fun day in the San Francisco sun. |
| | 16 | |
| | 17 | |
| | 18 | == Google Code In Ideas Instructions: == |
| | 19 | |
| | 20 | Please add your idea below in the following format: |
| | 21 | |
| | 22 | * Estimated hours: ? hours[[BR]] |
| | 23 | Categories: Whichever one or more of (i) code (ii) documentation/training (iii) outreach/research (iv) Quality Assurance (v) User Interface[[BR]] |
| | 24 | Boost libraries involved: Name these here[[BR]] |
| | 25 | Boost community members willing to check the work performed: List these here[[BR]] |
| | 26 | Description of the task |
| | 27 | |
| | 28 | Tasks should be chosen to be '''short''' with very well defined outcomes - it should be obvious to all when a task is done correctly or not. You should expect a majority of students to have no ability to program in C++, so try to restrict tasks to documentation, testing, working on the Boost website, designing graphics or icons, writing essays, blogs or videos about Boost libraries, that sort of thing. Do however throw in a few tasks for the more technically competent, such as helping to verify bugs sent to the issue tracker still occur against trunk, or even refactoring which is entirely mechanical but just a little too hard for file find regex and replace to do. |
| | 29 | |
| | 30 | [https://developers.google.com/open-source/gci/resources/example-tasks You find this list of past ideas for other projects of use to think about Boost project ideas]. |
| | 31 | |
| | 32 | == Google Code In Ideass: == |
