Difference between revisions of "Google Summer of Code 2014 Improvements"
Jump to navigation
Jump to search
(clone from 2013 page) |
|||
| Line 6: | Line 6: | ||
== 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 == | ||
| − | * See also '''[[Google Summer of Code 2013 Improvements|suggestions from last year]]''' and others from '''[[Google Summer of Code 2011 Improvements|2011]]''' and '''[[Google Summer of Code | + | * See also '''[[Google Summer of Code 2013 Improvements|suggestions from last year]]''' and others from '''[[Google Summer of Code 2011 Improvements|2011]]''' and '''[[Google Summer of Code 2012 Improvements|2012]]''' |
Latest revision as of 07:36, 17 November 2015
@ 
This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code
- See also suggestions from last year and others from 2011 and 2012
- Student recruiting: Applications are all about quality not quantity, but it's always great to get the number of students involved up as high as we can manage. This means a concerted advertising campaign and reaching out to schools and professors late Feb through early March. Ping your old profs! (HB)
- Add your idea here: Explain it here.
[Back to Google Summer of Code 2014 @ OSGeo]