Changes between Version 15 and Version 16 of GSoC/2021
- Timestamp:
- 02/12/21 12:06:59 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GSoC/2021
v15 v16 190 190 * 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. 191 191 * Be specific in the implementation (or at least as specific as you can). 192 * 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)192 * Explain what the final product will look like and how it will work. You can add drawings or mock-ups. 193 193 * Explain how the idea relates to existing GRASS GIS functions, features, and needs. 194 194 * 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. … … 197 197 * If you get stuck with the setup, feel free to consult the [https://lists.osgeo.org/listinfo/grass-user grass-user mailing list]. 198 198 * Familiarize yourself with wiki:Submitting rules. 199 * 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://github.com/OSGeo/grass/issues 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 beforeyou apply to GSoC.199 * 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://github.com/OSGeo/grass/issues 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. Do this before start you apply to GSoC. 200 200 * Also note that fixing existing bugs and/or implementing enhancements will be a part of student evaluation. 201 201