Difference between revisions of "Google Summer of Code 2018 Improvements"
Jump to navigation
Jump to search
Vrautenbach (talk | contribs) |
|||
| 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. | ||
| + | * Communication between mentors and student | ||
| + | : Use a tool, such as Trello, to setup to do lists and track progress of students. | ||
== Topics to be discussed at the upcoming Mentor summit == | == Topics to be discussed at the upcoming Mentor summit == | ||
Revision as of 20:23, 20 January 2019
@
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.
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.