Difference between revisions of "Google Summer of Code 2017 Improvements"
Jump to navigation
Jump to search
Wiki-Macho (talk | contribs) |
|||
Line 9: | Line 9: | ||
* '''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).? | Idea: Better bonding to community by sending the weekly report also to the developers mailing list (if it exists).? | ||
+ | |||
+ | * '''report template form''' | ||
+ | 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... | ||
+ | |||
== Topics to be discussed at the upcoming Mentor summit == | == Topics to be discussed at the upcoming Mentor summit == |
Revision as of 21:04, 4 September 2017
This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code
- 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).?
- report template form
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...
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 topic here: Explain it here.