GRASS GCI Ideas 2017: Difference between revisions
No edit summary |
No edit summary |
||
| Line 51: | Line 51: | ||
* added screenshots to {{cmd|d.grid}} {{rev|71930}} {{rev|71931}} {{rev|71932}} | * added screenshots to {{cmd|d.grid}} {{rev|71930}} {{rev|71931}} {{rev|71932}} | ||
* added screenshots to {{cmd|d.rast}} {{rev|71947}} {{rev|71948}} {{rev|71949}} | * added screenshots to {{cmd|d.rast}} {{rev|71947}} {{rev|71948}} {{rev|71949}} | ||
* added examples and screenshots to {{cmd|d.histogram}} {{rev|71956}} {{rev|71957}} {{rev|71958}} | |||
* added example and screenshot to {cmd|r.topidx}} {{rev|71959}} {{rev|71960}} {{rev|71961}} | |||
== Videos == | == Videos == | ||
Revision as of 22:58, 19 December 2017
@ 
@ 
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?
- 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
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
- improvements in i.albedo manual r71903 r71904 r71904
- added examples to r.support r71906 r71907 r71908
- added screenshot to d.rgb r71924 r71925 r71926
- added screenshot to d.mon r71927 r71928 r71929
- added screenshots to d.grid r71930 r71931 r71932
- added screenshots to d.rast r71947 r71948 r71949
- added examples and screenshots to d.histogram r71956 r71957 r71958
- added example and screenshot to {cmd|r.topidx}} r71959 r71960 r71961
Videos
How to create a location
Design a splash screen for GRASS GIS GUI start-up
- added tfang version r71941