Difference between revisions of "GRASS GCI Ideas 2017"

From GRASS-Wiki
Jump to: navigation, search
(+ screenshots added to manual pages - GCI students contribution)
Line 45: Line 45:
  
 
== Commits related to CGI 2017 ==
 
== Commits related to CGI 2017 ==
* improvements in i.albedo manual {{rev|71903}} {{rev|71904}} {{rev|71904}}
+
* improvements in {{cmd|i.albedo}} manual {{rev|71903}} {{rev|71904}} {{rev|71904}}
* added examples to r.support {{rev|71906}} {{rev|71907}} {{rev|71908}}
+
* added examples to {{cmd|r.support}} {{rev|71906}} {{rev|71907}} {{rev|71908}}
* added screenshot to r.rgb {{rev|71924}} {{rev|71925}} {{rev|71926}}
+
* added screenshot to {{cmd|d.rgb}} {{rev|71924}} {{rev|71925}} {{rev|71926}}
 +
* added screenshot to {{cmd|d.mon}} {{rev|71927}} {{rev|71928}} {{rev|71929}}
 +
* added screenshot to {{cmd|d.grid}} {{rev|71930}} {{rev|71931}} {{rev|71932}}
  
 
== Design a splash screen for GRASS GIS GUI start-up ==
 
== Design a splash screen for GRASS GIS GUI start-up ==

Revision as of 00:39, 13 December 2017

Grasslogo vector small.png @ GCI-logo.jpg @ Osgeo-logo.png

About

This is the GRASS page for Google Code-In 2017. Here we will list task ideas and other information related to the GRASS GCI projects.

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 Google Code-In main page.

How does it work?

  1. Students search for a task that interests them and claim it. They have at least three days and up to five to complete it.
  2. The student works on the task, getting guidance from mentors, if needed.
  3. Once the student has finished, he/she submits the work for review through the contest website.
  4. 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!
  5. Go to step #1 and repeat!

More details can be found at: 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 here.

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

Note: To sign up as a mentor, write an email to: gsoc-admin@osgeo.org.

Results

Commits related to CGI 2017

Design a splash screen for GRASS GIS GUI start-up