Google Summer of Code 2019 Improvements

From OSGeo
Revision as of 01:18, 5 September 2019 by Wiki-Ismailsunni (talk | contribs)
Jump to navigation Jump to search

GSoC2016Logo.jpg @ Osgeo-logo.png

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

  • See also lesson learned from 2018, 2017, 2015, 2014, 2013, 2012, 2011
  • Attending community meeting: Attending community meeting (e.g. QGIS hackfest/contributor meeting, FOSS4G conference) can make the student feel more part of the community (meet other community members). It also helps the student to discuss faster with the mentors.
  • Final report: Template for the final report in the mailing list is great. Unfortunatelly, it's not so good looking and easy to find for future reference. I suggest to make a simple web page that can easily shareable and have interesting format/look. It can be used as the link to the "code url" in the GSoC website. Static page like Github page is good for example. Github wiki page is good also, but there are some limitation (e.g. can't embed video, the URL is quite long)
  • Add your idea here: Explain it here.

Topics to be discussed at the upcoming Mentor summit

Google mentor summit is a great occasion to meet other organizations and gsoc admins and share good practices, clarify doubts, discuss potential problems and possible improvements. There is always room for improvement! So please, list hereinafter suggestions on topics that you wish your OSGeo delegates should bring to mentor summit for discussion.

  • Add your idea here: Explain it here.