View source for GRASS GCI Ideas 2018

<center>
[[Image:grasslogo_vector_small.png|link=http://grass.osgeo.org]]<font size="+3"> @ </font> [[Image:GCI-logo.jpg|300px|link=https://developers.google.com/open-source/gci/]] <font size="+3"> @ </font> [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

= About =

This is the GRASS page for [https://wiki.osgeo.org/wiki/Google_Code_In_2017 Google Code-In] 2017. Here we will list task ideas and other information related to the GRASS GCI projects as well as the contest results and contributions by the students.

== What is Google Code-In? ==

Pre-university students ages 13 to 17 are invited to take part in Google Code-in: Our global, online, contest introducing teenagers to the world of open source. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have. Mentors from our participating organizations lend a helping hand as participants learn what it’s like to work on an open source project. For more details, see [https://developers.google.com/open-source/gci/ Google Code-In] main page. 

== How does it work? ==

#  Students search for a '''task''' that interests them and claim it. They have at least ''three days and up to five'' to complete it.
#  The student works on the task, getting guidance from mentors, if needed.
#  Once the student has finished, he/she submits the work for review through the contest website.
#  Mentors from the organization evaluate the work, provide feedback, and if it's complete, accept it! Otherwise, specific feedback is provided, and the student goes back to step #2!
#  Go to step #1 and repeat!

More details can be found at: [https://developers.google.com/open-source/gci/how-it-works https://developers.google.com/open-source/gci/how-it-works]

== Tasks ==

The organizations should create a large list of short (3-5 hour) tasks for students to work on. Tasks are categorized as: Code, Documentation/Training, Outreach/Research, Quality Assurance, or User Interface. Some examples of tasks of different categories can be found [https://developers.google.com/open-source/gci/resources/example-tasks here].

=== Some ideas for tasks ===

* Create a screenshot for the next 76 release announcement 
* Design the t-shirt for the next code-sprint
* Add examples to manual pages
* Make a promo video for GRASS GIS
* Make new tutorial videos for GRASS GIS
* Write a short blog entry about GRASS GIS (or a certain module)
* Enhance the visual index
* Make screenshots to populate the visual change log in new features pages (e.g., for [https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures76 New Features GRASS 7.6])
* Create icons/phrases to include in sticker sheets
* Give a talk about GRASS GIS to classmates
* Contribute examples based on NC dataset to manual pages (extensive to add-ons)
* Contribute screenshots to manual pages (extensive to add-ons)
* Submit a patch for a certain bug or enhancement ticket
* Contribute tests for modules
* ''add your own idea...''

== Details about the tasks and lessons learnt ==

* Translations are not allowed by Google Code In as tasks.

* A strategic plan is needed to generate a pool of tasks doable in 3-5 hours (from beginner to advanced tasks); '''from ~50 up to ~100 tasks!!'''

* A '''large mentor pool''' that can tackle evaluations of about ~ 100 tasks!! Importantly, the revision of tasks should be rather quick, since the students should complete as many tasks as possible to win the contest.

= Available mentors =
List of available mentors to follow the tasks

* [[User:Lucadelu|Luca Delucchi]]
* [[User:Veroandreo|Veronica Andreo]]
* ...

'''Important''': To sign up as a mentor, write an email to: gci-admin at osgeo dot org

[[Category: Development]]
[[Category: Community]]