Difference between revisions of "Google Summer of Code 2015 Improvements"

From OSGeo
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Image:GoogleSummer_2015logo.jpg|350px|link=http://code.google.com/soc/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
+
<center>
 +
[[Image:GoogleSummer_2015logo.jpg|200px|link=http://code.google.com/soc/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]
 +
</center>
  
 
== This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code ==
 
== This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code ==
Line 7: Line 9:
 
* ''' Selection of the students''' : the submission of at least a non trivial patch should be made compulsory by the mentors in order to see if the student is familiar enough with the coding environment and the software.
 
* ''' Selection of the students''' : the submission of at least a non trivial patch should be made compulsory by the mentors in order to see if the student is familiar enough with the coding environment and the software.
  
* ''' Foster collaboration''' among geo-related GSoC, cross link like minded projects from wiki page etc.. See [https://lists.osgeo.org/pipermail/soc/2015-November/003128.html here]
+
* ''' Foster collaboration''' among geo-related GSoC, cross link like-minded projects from wiki page etc.. See [https://lists.osgeo.org/pipermail/soc/2015-November/003128.html here]
  
 
* '''Wrap up''': It is important to create the 'results' wiki page year by year, otherwise we lose track of the work done so far. Also good to ask the students to make a slide and write a paragraph, addressed to the broader community, in order to showcase the projects to people that have not followed the progresses of the students. Something like [https://lists.osgeo.org/pipermail/soc/2015-November/003129.html this]. The slides can be used at the mentors summit.
 
* '''Wrap up''': It is important to create the 'results' wiki page year by year, otherwise we lose track of the work done so far. Also good to ask the students to make a slide and write a paragraph, addressed to the broader community, in order to showcase the projects to people that have not followed the progresses of the students. Something like [https://lists.osgeo.org/pipermail/soc/2015-November/003129.html this]. The slides can be used at the mentors summit.
 +
 +
* '''Wiki pages related to GSoC''': Try to avoid duplicates, maintain all general info in single pages rather than annual pages repeating always the same: e.g. recommendations to students, etc.
  
 
* '''Add your idea here''': Explain it here.
 
* '''Add your idea here''': Explain it here.

Latest revision as of 07:52, 17 November 2015

GoogleSummer 2015logo.jpg @ OSGeo 300 127 pixel.png

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

  • Selection of the students : the submission of at least a non trivial patch should be made compulsory by the mentors in order to see if the student is familiar enough with the coding environment and the software.
  • Foster collaboration among geo-related GSoC, cross link like-minded projects from wiki page etc.. See here
  • Wrap up: It is important to create the 'results' wiki page year by year, otherwise we lose track of the work done so far. Also good to ask the students to make a slide and write a paragraph, addressed to the broader community, in order to showcase the projects to people that have not followed the progresses of the students. Something like this. The slides can be used at the mentors summit.
  • Wiki pages related to GSoC: Try to avoid duplicates, maintain all general info in single pages rather than annual pages repeating always the same: e.g. recommendations to students, etc.
  • Add your idea here: Explain it here.