Changes between Version 10 and Version 11 of GSoC/2019


Ignore:
Timestamp:
02/09/19 02:11:38 (6 years ago)
Author:
neteler
Comment:

http --> https

Legend:

Unmodified
Added
Removed
Modified

  • GSoC/2019

    v10 v11  
    2828== About ==
    2929
    30  * [http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019 The OSGeo GSoC 2019 main page]
     30 * [https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019 The OSGeo GSoC 2019 main page]
    3131 * [https://summerofcode.withgoogle.com/ Official GSoC page at Google]
    3232
    3333== Ideas ==
    3434
    35 ''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.''
    36 
    37 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].
    38 
    39 ''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],
    40 [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2009#Ideas 2009], [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2010#Ideas 2010],
    41 [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2011#Ideas 2011], [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2012#Ideas 2012],
    42 [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/2018 2018])
     35''Post your ideas here or to the [https://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 [https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/ OSGeo Userid]; read also some [wiki:TracLinks help] for using trac.''
     36
     37If you are a student you can suggest an new idea or pick up an existing one in any case write about it to [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].
     38
     39''You are invited as well to have a close look at (and re-suggest!) ideas from previous years ([https://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2007 2007], [https://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2008#Ideas 2008],
     40[https://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2009#Ideas 2009], [https://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2010#Ideas 2010],
     41[https://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2011#Ideas 2011], [https://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2012#Ideas 2012],
     42[https://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/2018 2018])
    4343which have not yet been implemented.
    4444You can also look at accepted GRASS GSoC [wiki:GSoC projects from previous years] for an idea of scope.''
    … …  
    196196  * Mailing list and wikis:
    197197   * [https://lists.osgeo.org/pipermail/grass-dev/2018-March/087764.html grass-dev New CLI GSoC Idea: Comments, Mentors, Students Needed] (whole thread)
    198    * [http://lists.osgeo.org/pipermail/grass-dev/2015-January/072979.html grass-dev QGIS Processing & GRASS (January 2015)]
    199    * [http://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly Working with GRASS without starting it explicitly]
     198   * [https://lists.osgeo.org/pipermail/grass-dev/2015-January/072979.html grass-dev QGIS Processing & GRASS (January 2015)]
     199   * [https://grasswiki.osgeo.org/wiki/Working_with_GRASS_without_starting_it_explicitly Working with GRASS without starting it explicitly]
    200200   * wiki:Grass7/VectorLib/OGRInterface
    201201   * wiki:Grass7/VectorLib/PostGISInterface
    … …  
    203203   * [https://github.com/qgis/QGIS/blob/0a1382a0be36d408aebd227fb0066f68c513e41e/python/plugins/processing/algs/grass7/Grass7Algorithm.py QGIS Processing Grass7Algorithm.py] source code
    204204   * [https://github.com/moovida/jgrasstools/blob/530c87f26d220f3eeff9d2fb9d21abd8821c00c3/grass/src/main/java/org/jgrasstools/grass/utils/ModuleSupporter.java uDig's JGrasstools] source code
    205    * [http://sextante.googlecode.com/svn/trunk/soft/sextante_lib/sextante_gui/src/es/unex/sextante/gui/grass/ SEXTANTE grass] source code (broken link)
    206    * [https://github.com/geopython/PyWPS/blob/425f0eb160f60714a6705a24ba926e03690ab371/pywps/Grass.py PyWPS source code] and [http://pywps.wald.intevation.org/documentation/process.html PyWPS documentation] (broken link)
     205   * [https://sextante.googlecode.com/svn/trunk/soft/sextante_lib/sextante_gui/src/es/unex/sextante/gui/grass/ SEXTANTE grass] source code (broken link)
     206   * [https://github.com/geopython/PyWPS/blob/425f0eb160f60714a6705a24ba926e03690ab371/pywps/Grass.py PyWPS source code] and [https://pywps.wald.intevation.org/documentation/process.html PyWPS documentation] (broken link)
    207207   * [https://code.google.com/p/wps-grass-bridge/source/browse/trunk/?r=97 wps-grass-bridge] source code (broken link)
    208208   * Related discussions on mailing list:
    209     * [http://lists.osgeo.org/pipermail/grass-dev/2015-February/073867.html On GSoC Proposal New easy-to-use...]
    210     * [http://lists.osgeo.org/pipermail/grass-dev/2015-March/074433.html GSOC project proposal]
     209    * [https://lists.osgeo.org/pipermail/grass-dev/2015-February/073867.html On GSoC Proposal New easy-to-use...]
     210    * [https://lists.osgeo.org/pipermail/grass-dev/2015-March/074433.html GSOC project proposal]
    211211   * Similar complex command line interfaces to learn from:
    212212    * Git (a classic example of subcommand interface)
    … …  
    241241== Tips for students ==
    242242
    243  * 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].
    244  * 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.
     243 * If you have your own ideas we encourage you to propose them. Explain them on the [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].
     244 * If you like some idea here or from previous yeas, write about it on [https://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list] and any ideas of your own which could improve it.
    245245 * Follow some good practices in your ideas and proposals:
    246246  * Stress why the project would be useful.
    … …  
    251251  * 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.
    252252 * Compile GRASS GIS 7 (trunk) from source and prepare environment for development:
    253   * See links appropriate for you at [http://grass.osgeo.org/development/how-to-start/].
    254   * If you get stuck with the setup, feel free to consult the [http://lists.osgeo.org/listinfo/grass-user grass-user mailing list].
     253  * See links appropriate for you at [https://grass.osgeo.org/development/how-to-start/].
     254  * If you get stuck with the setup, feel free to consult the [https://lists.osgeo.org/listinfo/grass-user grass-user mailing list].
    255255  * Familiarize yourself with wiki:Submitting rules.
    256  * 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.
     256 * Prove your worth by being active on the GRASS mailing lists ([https://lists.osgeo.org/listinfo/grass-user grass-user], [https://lists.osgeo.org/listinfo/grass-dev grass-dev]), fix some [https://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.
    257257 * Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation.
    258258
    259  * 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].
     259 * Every year GRASS GIS hopes to participate and participates in GSoC as part of the [https://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_2019 OSGeo GSoc Ideas page].