204 | | * Explain how the final product will look like, how do we use it, perhaps, you can add some drawings (here to the wiki page) |
205 | | * Explain how the idea relates to existing GRASS GIS functions and features. |
206 | | * Don't include steps such as "install GRASS" or "compile GRASS libraries (on my machine)", you should do this before GSoC. |
| 204 | * 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) |
| 205 | * Explain how the idea relates to existing GRASS GIS functions, features, and needs. |
| 206 | * 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. |
209 | | * If you struggle with it, consult at [http://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list]. |
210 | | * See also SUBMITTING files in source code. |
211 | | * Be active on 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], implement some (smaller) features, or write some (simpler) GRASS module (and post it to mailing list) to show your willingness and abilities. |
212 | | * Note that GRASS GIS is participiating as part of [http://www.osgeo.org/ OSGeo]. See the official OSGeo template for application and other information at the [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2014_Ideas OSGeo GSoc Ideas page]. |
| 209 | * If you get stuck with the setup, feel free to consult the [http://lists.osgeo.org/listinfo/grass-user grass-user mailing list]. |
| 210 | * Familiarize yourself with the various SUBMITTING files in the top level of the source code. |
| 211 | * 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. |
| 212 | |
| 213 | * GRASS GIS hopes to participate 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 [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2014_Ideas OSGeo GSoc Ideas page]. |