Difference between revisions of "GRASS GCI Ideas 2017"

From GRASS-Wiki
Jump to: navigation, search
(creating Google Code In 2017 Ideas collection page)
 
(some extra details)
Line 1: Line 1:
== About ==
+
= 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 and other information related to the GRASS GCI projects.
+
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.
  
== Ideas ==
+
= Ideas for tasks =
  
Some ideas so far:
+
Some ideas collected so far:
  
* Create screenshot for the next 74 release announcement
+
* Create a screenshot for the next 74 release announcement  
 
* Design the t-shirt for the next code-sprint
 
* Design the t-shirt for the next code-sprint
 
* Add examples to manual pages
 
* Add examples to manual pages
Line 13: Line 13:
 
* Make new tutorial videos for GRASS GIS
 
* Make new tutorial videos for GRASS GIS
 
* Enhance the visual index
 
* Enhance the visual index
* Make screenshots for release pages (visual change-log)
+
* Make screenshots to populate the visual change log in new features pages (e.g., for [https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74 New Features GRASS 7.4])
* Submiting patch for a certain bug or enhancement ticket
+
* Create icons/phrases to include in sticker sheets
 +
* Give a talk about GRASS GIS to classmates
 +
* Submit a patch for a certain bug or enhancement ticket
 
* Contribute tests for modules
 
* Contribute tests for modules
* Create icons/phrases for sticker sheets
+
* ''add your own idea...''
* Give a talk about GRASS GIS to classmates
+
 
* ... add your own idea
+
== Details about the tasks ==
 +
 
 +
There should be some very simple and introductory tasks such as installing GRASS GIS and making a screenshot, intermediate tasks, and more advanced ones as those involving a bit (more) of coding. A certain large task might also be split into smaller tasks.
 +
 
 +
Those general ideas like "make examples for manual pages" might then be replicated for several modules, for example, and each one will constitute a task.
 +
 
 +
Translations are not allowed by Google Code In as tasks.
 +
 
 +
<!-- Please, edit this page and add further info -->

Revision as of 12:58, 2 October 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.

Ideas for tasks

Some ideas collected so far:

  • Create a screenshot for the next 74 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
  • Enhance the visual index
  • Make screenshots to populate the visual change log in new features pages (e.g., for New Features GRASS 7.4)
  • Create icons/phrases to include in sticker sheets
  • Give a talk about GRASS GIS to classmates
  • Submit a patch for a certain bug or enhancement ticket
  • Contribute tests for modules
  • add your own idea...

Details about the tasks

There should be some very simple and introductory tasks such as installing GRASS GIS and making a screenshot, intermediate tasks, and more advanced ones as those involving a bit (more) of coding. A certain large task might also be split into smaller tasks.

Those general ideas like "make examples for manual pages" might then be replicated for several modules, for example, and each one will constitute a task.

Translations are not allowed by Google Code In as tasks.