Google Summer of Code 2017 Administrative - Revision history

Hellik: /* Contacts */

2018-08-25T04:15:41Z

Contacts

Jmckenna at 13:51, 7 September 2017

2017-09-07T13:51:03Z

Madi: /* Mentor Summit */

2017-07-31T06:54:13Z

Mentor Summit

Jmckenna at 16:42, 26 July 2017

2017-07-26T16:42:56Z

Madi: /* Bad ideas */

2017-04-13T13:50:04Z

Bad ideas

Madi: /* Bad ideas */

2017-04-13T13:49:29Z

Bad ideas

Madi: /* Bad ideas */

2017-04-13T13:42:11Z

Bad ideas

Madi: /* Good ideas */

2017-04-13T13:39:46Z

Good ideas

Madi: /* Good ideas */

2017-04-13T13:31:47Z

Good ideas

Madi: /* Bad ideas */

2017-04-13T13:30:31Z

Bad ideas

@@ Line 23: / Line 23: @@
 ** join the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])
-* [[User:Madi|Margherita Di Leo]] acts as chair of the Admin team, which includes [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], [[Jeff McKenna]], and Guillermo Pizarro. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!
+* [[User:Madi|Margherita Di Leo]] acts as chair of the Admin team, which includes [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], [[Jeff McKenna]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!
 <!-- Admins: please add your pictures here -->

@@ Line 1: / Line 1: @@
 <center>
-[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
+[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font> [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
 </center>

@@ Line 377: / Line 377: @@
 == Mentor Summit ==
-Each year Google hosts the "Mentor Summit" event at their headquarters.  The tentative date for this year is: [https://groups.google.com/forum/#!msg/google-summer-of-code-mentors-list/OTwNTCujKDA/HuhFQQauAgAJ October 13-15 2017].  This year we are developing guidelines for who can represent OSGeo at the summit: see https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Mentor_Summit
+Each year Google hosts the "Mentor Summit" event at their headquarters.  The tentative date for this year is: [https://groups.google.com/forum/#!msg/google-summer-of-code-mentors-list/OTwNTCujKDA/HuhFQQauAgAJ October 13-15 2017].  This year we are developing guidelines for who can represent OSGeo at the summit: see [[Google Summer of Code 2017 Mentor Summit]]
 == Learn more ==

← Older revision		Revision as of 16:42, 26 July 2017
Line 374:		Line 374:

	* ...		* ...
		+
		+	== Mentor Summit ==
		+
		+	Each year Google hosts the "Mentor Summit" event at their headquarters. The tentative date for this year is: [https://groups.google.com/forum/#!msg/google-summer-of-code-mentors-list/OTwNTCujKDA/HuhFQQauAgAJ October 13-15 2017]. This year we are developing guidelines for who can represent OSGeo at the summit: see https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Mentor_Summit

	== Learn more ==		== Learn more ==

@@ Line 371: / Line 371: @@
 * If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care of having many projects developed, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
 * If you are the kind of person always whining about the rules, please abstain becoming a mentor. '''GSoC has many rules''', and most of them are set by Google so there is no way to change them, at least for the current GSoC. In general, GSoC rules are set for a reason, that you may or may not know, so the simplest way is either to accept them as a matter of fact or not participating at all.
-* It is a bad idea not paying attention to '''confidential information'''. Proposals ranking, comments on students work and background are exchanged via email. You need always to pay attention to the confidentiality of the content when you forward bits of emails to someone else that was not in the receivers in the first place. Furthermore, even if you know beforehand the results of selection or student evaluation, you must pay attention not to break the news to the students before they are informed by Google.
+* It is a bad idea not paying attention to '''confidential information'''. Proposals ranking, comments on students work and background are exchanged via email. You need always to pay attention to the confidentiality of the content when you forward bits of emails to someone else that was not in the receivers in the first place. Furthermore, even if you know beforehand the results of selection or student evaluation, you must pay attention '''not to break the news''' to the students before they are informed by Google.
 * ...

@@ Line 369: / Line 369: @@
 === Bad ideas ===
-* If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care to have many GSoC projects, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
+* If you do not always '''meet the deadlines''', and do not always '''read the emails''', if you feel that you '''don't have time''', even if you really want to see a certain GSoC idea developed, it is a bad idea to consider becoming a mentor. GSoC deadlines are hard deadlines. All GSoC instructions are given via email. We do not much care of having many projects developed, but we'd rather have less, quality, well mentored projects, and '''students cannot be abandoned halfway'''.
 * If you are the kind of person always whining about the rules, please abstain becoming a mentor. '''GSoC has many rules''', and most of them are set by Google so there is no way to change them, at least for the current GSoC. In general, GSoC rules are set for a reason, that you may or may not know, so the simplest way is either to accept them as a matter of fact or not participating at all.

@@ Line 355: / Line 355: @@
 === Good ideas ===
-* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page.
+* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand their capability. Think about coding tasks much earlier than the deadline, and connect the task to the idea in the ideas page, as tasks should reflect the skills required to develop a certain idea.
 * Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.
-* A earlier mentor reported: "In my experience, it's most effective to require an accepted pull request of developed code by end of summer and write the proposal in terms of getting there."
+* A former mentor reported: "In my experience, it's most effective to require an accepted pull request of developed code by end of summer and write the proposal in terms of getting there."
-* It is key '''getting to know the student before the project starts''', in order to adapt the workload to his/her capabilities. It can be good to get in touch via hangout and make a sort of general interview, beside challenging them with a code test.
+* It is key '''getting to know the students before the project starts''', in order to adapt the workload to their capabilities. In the proposal template, students are asked basic information about their background, studies and experience, but some mentors report that it can be good to get in touch via hangout or similar voip and make a sort of general interview, beside challenging them with a coding challenge.
-* If the student struggles during the gsoc, get in touch and try to understand what is wrong and try to '''adjust the objectives''' according to what is possible for the student to achieve.
+* If the student struggles during the GSoC, get in touch and try to understand what is wrong and try to '''adjust the objectives''' according to what is possible for the student to achieve.
-* It is often convenient to '''split the work into smaller tasks''' corresponding to clear deliverables. In this way, it is easier to track the progress, both for student and mentors.
+* It is often convenient to '''split the work into smaller tasks''' / clear deliverables. This way, it is easier to track the progress, both for student and mentors.
 * If the student doesn't feel oppressed with nearly impossible requests, (s)he is more likely to learn with a fresh mind and '''stick in the community''' after GSoC ends and perhaps become a mentor or somehow help out with the GSoC subsequently.
 * '''Talking in conferences''' does attract quality students to apply to GSoC

@@ Line 363: / Line 363: @@
 * If the student doesn't feel oppressed with nearly impossible requests, (s)he is more likely to learn with a fresh mind and '''stick in the community''' after GSoC ends and perhaps become a mentor or somehow help out with the GSoC subsequently.
 * '''Talking in conferences''' does attract quality students to apply to GSoC
-* '''GSoC lasts all year long''', beside the coding, it's advertising the program, attracting students, drafting ideas, cultivating mentor capacity, etc
+* '''GSoC activities span during all year''', beside the coding, it's advertising the program, attracting students, drafting ideas, cultivating mentor capacity, etc
 * ...