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

From OSGeo
Jump to navigation Jump to search
 
(5 intermediate revisions by 2 users not shown)
Line 8: Line 8:
 
* See also lesson learned from  [[Google Summer of Code 2017 Improvements|2017]], [[Google Summer of Code 2015 Improvements|2015]], [[Google Summer of Code 2014 Improvements|2014]], [[Google Summer of Code 2013 Improvements|2013]], [[Google Summer of Code 2012 Improvements|2012]], [[Google Summer of Code 2011 Improvements|2011]]
 
* See also lesson learned from  [[Google Summer of Code 2017 Improvements|2017]], [[Google Summer of Code 2015 Improvements|2015]], [[Google Summer of Code 2014 Improvements|2014]], [[Google Summer of Code 2013 Improvements|2013]], [[Google Summer of Code 2012 Improvements|2012]], [[Google Summer of Code 2011 Improvements|2011]]
 
* '''Add your idea here''': Explain it here.
 
* '''Add your idea here''': Explain it here.
−
Idea: Better bonding to community by sending the weekly report also to the developers mailing list (if it exists).?
+
* '''Communication between mentors and student'''
−
 
+
: Use a tool, such as Trello, to setup to do lists and track progress of students.
−
* '''report template form'''
+
: VLC community does a Face-to-Face meeting between their mentors and students.
−
Having a standardized form to fill in weekly reports would help students, mentors and admins to keep track of deadlines without jumping from link to link...
+
* '''Regular meetings (e.g. weekly) between mentors and student'''
−
 
+
: Regular meetings ensure that the mentors and students stay active. These meetings can be 10 minutes or longer, the idea is just to discuss the plan for the week, for example.  
−
* '''final report template'''
+
* '''Retaining students after GSoC'''
−
Creating a final report template in GIT would facilitate final reporting with all important,necessary and needed informations in the right place; just fork the template, fill in, it's done and submit the url.
+
: GSoC is a good opportunity to increase the capacity with in the community. Work on a strategy to make the students feel more part of the community and contribute in the future.
−
 
 
−
*'''collective chat for students'''
 
−
Creating a common chat platform for students on e.g. Slack. This would help with staying in touch with them, communication could go faster between us Admins and mentors. Moreover, students could share resources between them, experiences how they managed to overcome certain difficulties, this came of great help for  GSoC newtimers. If moderated correctly with a little bit of effort this can turn into a very good thing community-wise, bonding between students, increase collaboration, reinforce the ideas of an open source community.
 
−
 
 
  
 
== Topics to be discussed at the upcoming Mentor summit ==
 
== Topics to be discussed at the upcoming Mentor summit ==
Line 24: Line 20:
 
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.
 
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.
  
−
* '''emphasize bonding period''': Community bonding period is a good chance to learn how to communicate with and how to learn from the community. it seems this chance is very little used by students. How do other orgs motivate students to be active in community bonding period.
+
* '''Add your idea here''': Explain it here.
 +
 
  
  
  
 
[[Category:Google Summer of Code]]
 
[[Category:Google Summer of Code]]

Latest revision as of 08:36, 23 January 2019

GSoC2016Logo.jpg @ Osgeo-logo.png

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

  • See also lesson learned from 2017, 2015, 2014, 2013, 2012, 2011
  • Add your idea here: Explain it here.
  • Communication between mentors and student
Use a tool, such as Trello, to setup to do lists and track progress of students.
VLC community does a Face-to-Face meeting between their mentors and students.
  • Regular meetings (e.g. weekly) between mentors and student
Regular meetings ensure that the mentors and students stay active. These meetings can be 10 minutes or longer, the idea is just to discuss the plan for the week, for example.
  • Retaining students after GSoC
GSoC is a good opportunity to increase the capacity with in the community. Work on a strategy to make the students feel more part of the community and contribute in the future.

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.
Retrieved from "http://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2018_Improvements&oldid=119321"