Changes between Version 61 and Version 62 of GSoC/2014

Timestamp:

Feb 16, 2014, 2:47:25 PM (10 years ago)

Author:

hamish

Comment:

minor wording

GSoC/2014

@@ -196 +196 @@
 == For students ==
 
- * If you have your own ideas, 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].
+ * 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 what how you will proceed. Make sure that what you propose is feasible.
+  * 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 how the final product will look like, how do we use it, perhaps, you can add some drawings (here to the wiki page)
-  * Explain how the idea relates to existing GRASS GIS functions and features.
-  * Don't include steps such as "install GRASS" or "compile GRASS libraries (on my machine)", you should do this before GSoC.
+  * 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 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 struggle with it, consult at [http://lists.osgeo.org/listinfo/grass-dev grass-dev mailing list].
-  * See also SUBMITTING files in source code.
- * 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.
- * 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].
+  * 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 the various SUBMITTING files in the top level of the source code.
+ * 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.
+
+ * 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].