{{{
#!html
<!-- direct usage of HTML enables to use the big @ characters at the same line as images -->
<!-- derived from the HTML taken from GRASS User Mediawiki -->
<!-- needs to be changed every year (GSoC link and maybe picture) -->
<!-- also check and update links at the bottom -->
<p>
<a href="https://grass.osgeo.org" rel="nofollow">
<img alt="Grasslogo vector small.png" src="/grass/raw-attachment/wiki/GSoC/2014/Grasslogo_vector_small.png" width="110" height="123" />
</a>
 <font size="+3"> @ </font>
<a href="https://summerofcode.withgoogle.com/" rel="nofollow">
<img alt="500px-GSoC2016Logo.jpg​" src="/grass/raw-attachment/wiki/GSoC/2016/500px-GSoC2016Logo.jpg"/>
</a>
<font size="+3"> @ </font>
<a href="https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2018" rel="nofollow">
<img alt="OSGeo logo" src="/grass/raw-attachment/wiki/GSoC/2018/osgeo_logo.png" width="300" height="97" /></a>
</p> 
}}}


= GRASS Google Summer of Code 2019 =

[[TOC]]


== About ==

 * [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019 The OSGeo GSoC 2019 main page]
 * [https://summerofcode.withgoogle.com/ Official GSoC page at Google]

== Ideas ==

''Post your ideas here or to the [http://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list] if you want to discuss them more. To edit this wiki, you need to [https://trac.osgeo.org/grass/login login] with an [http://www.osgeo.org/osgeo_userid OSGeo Userid]; read also some [wiki:TracLinks help] for using trac.''

If you are a student you can suggest an new idea or pick up an existing one in any case write about it to [http://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].

''You are invited as well to have a close look at (and re-suggest!) ideas from previous years ([http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2007 2007], [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2008#Ideas 2008],
[http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2009#Ideas 2009], [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2010#Ideas 2010],
[http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2011#Ideas 2011], [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2012#Ideas 2012],
[http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013#Ideas 2013], [wiki:/GSoC/2014 2014], [wiki:/GSoC/2015 2015], [wiki:/GSoC/2016 2016], [wiki:/GSoC/2017 2017], [wiki:/GSoC/2017 2018]) which have not yet been implemented.
You can also look at accepted GRASS GSoC [wiki:GSoC projects from previous years] for an idea of scope.''

''Include "GRASS GIS" in the title of our idea to easily distinguish ideas and projects inside OSGeo.''

''Some bigger ideas may have their own pages, so you can link them here. The pages can be either independent if the page already exists (e.g. `wxGUIDevelopment/SingleWindow`), or more preferably subpages of this page if the idea is (re-)developed for this GSoC. In the later case, use the word "idea" in the page name to distinguish the idea page (e.g. `GSoC/2017/CoolGRASSProjectIdea`) from the possible student project page (e.g. `GSoC/2017/CoolGRASSProject`).''



=== Title of idea ===

Description here

* Requirements: 
* Mentor: 
* Proposed by: 
* Rating: 
* Expected Outcomes:  
* Test of skills: 
* Other: 



== Tips for students ==

 * If you have your own ideas we encourage you to propose them. Explain them on the [http://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].
 * If you like some idea here or from previous yeas, write about it on [http://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list] and any ideas of your own which could improve it.
 * Follow some good practices in your ideas and proposals:
  * Stress why the project would be useful.
  * Show that you know how you will proceed. That is, make sure that you can demonstrate that the proposal is feasible in the given time frame.
  * Be specific in the implementation (or at least as specific as you can).
  * Explain what the final product will look like and how it will work. Perhaps you can add some drawings or mock-ups. (here in a wiki page)
  * Explain how the idea relates to existing GRASS GIS functions, features, and needs.
  * Do not include steps such as "install GRASS", "compile GRASS libraries (on my machine)", "read about the API". You should do this before applying to GSoC.
 * Compile GRASS GIS 7 (trunk) from source and prepare environment for development:
  * See links appropriate for you at [http://grass.osgeo.org/development/how-to-start/].
  * If you get stuck with the setup, feel free to consult the [http://lists.osgeo.org/listinfo/grass-user grass-user mailing list].
  * Familiarize yourself with wiki:Submitting rules.
 * Prove your worth by being active on the GRASS mailing lists ([http://lists.osgeo.org/listinfo/grass-user grass-user], [http://lists.osgeo.org/listinfo/grass-dev grass-dev]), fix some [http://trac.osgeo.org/grass/report bugs], and/or implement some (smaller) features, or write some (simpler) GRASS module, and post it to mailing list. There's no better way to demonstrate your willingness and abilities. You should start even before you apply to GSoC. 
 * Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.

 * Every year GRASS GIS hopes to participate and participates in GSoC as part of the [http://www.osgeo.org/ OSGeo Foundation]'s GSoC program umbrella. See the official OSGeo template for application details and other important information at the [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017 OSGeo GSoc Ideas page].