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

From OSGeo
Jump to navigation Jump to search
Line 5: Line 5:
 
* See also lesson learned from  '''[[Google Summer of Code 2011 Improvements|2011]]'''; '''[[Google Summer of Code 2012 Improvements|2012]]'''; '''[[Google Summer of Code 2013 Improvements|2013]]''' ;'''[[Google Summer of Code 2014 Improvements|2014]]'''
 
* See also lesson learned from  '''[[Google Summer of Code 2011 Improvements|2011]]'''; '''[[Google Summer of Code 2012 Improvements|2012]]'''; '''[[Google Summer of Code 2013 Improvements|2013]]''' ;'''[[Google Summer of Code 2014 Improvements|2014]]'''
  
 
+
* '''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.
  
 
* '''Add your idea here''': Explain it here.
 
* '''Add your idea here''': Explain it here.

Revision as of 07:40, 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

  • 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.
  • Add your idea here: Explain it here.