Google Summer of Code 2013 Improvements

From OSGeo
Jump to navigation Jump to search

Gsoc-2013-logo-color.jpg @ OSGeo 300 127 pixel.png


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


See last year's improvement suggestions page for more details. --HB
  • IRC: We've launched an OSGeo GSoC IRC channel: #osgeo-soc on the Freenode network. Should we actively promote it or try to keep things on the ML? i.e. foster informal peer support among the students/mentors beyond the weekly reports. --HB
  • FOSS4G-NA meetup: Anyone going to FOSS4G-NA in Minneapolis, May 22–24? It would be great to have a birds-of-a-feather meetup of mentors and prospective students! --HB
going? let us know :)
  • Better define community bonding period: Note this time should also be used for doing further reading and getting the full build toolchain working -- the latter being a great excuse to have a little back and forth with the community, asking for tips about the best way to configure it and send patches etc. Coding should begin at the start; the summer is too short to let 3rd week reports of "still doing some reading about it and trying to get it to build" happen. --HB
  • Add your idea here: Explain it here.


[Back to Google Summer of Code 2013 @ OSGeo]