| | 68 | == For students == |
| | 69 | |
| | 70 | * If you have your own ideas, propose them, explain them on the [http://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list]. |
| | 71 | * 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]. |
| | 72 | * Follow some good practices in your ideas and proposals: |
| | 73 | * Stress why the project would be useful. |
| | 74 | * Show that you know what how you will proceed. Make sure that what you propose is feasible. |
| | 75 | * Be specific in the implementation (or at least as specific as you can). |
| | 76 | * Explain how the final product will look like, how do we use it, perhaps, you can add some drawings (here to the wiki page) |
| | 77 | * Explain how the idea relates to existing GRASS GIS functions and features. |
| | 78 | * Don't include steps such as "install GRASS" or "compile GRASS libraries (on my machine)", you should do this before GSoC. |
| | 79 | * Compile GRASS 7 (trunk) from source and prepare environment for development: |
| | 80 | * See links appropriate for you at [http://grass.osgeo.org/development/how-to-start/]. |
| | 81 | * If you struggle with it, consult at [http://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list]. |
| | 82 | * See also SUBMITTING files in source code. |
| | 83 | * 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. |
| | 84 | |
| | 85 | |
