Google Summer of Code 2017 Mentor Summit - Revision history

Wiki-Iamrohith94: /* Day 2 */

2017-11-03T17:23:22Z

Day 2

Wiki-Iamrohith94 at 17:22, 3 November 2017

2017-11-03T17:22:00Z

Madi: /* Report from Margherita Di Leo */

2017-11-01T11:56:30Z

Report from Margherita Di Leo

Madi: /* Report from Margherita Di Leo */

2017-11-01T11:54:09Z

Report from Margherita Di Leo

Madi at 11:39, 1 November 2017

2017-11-01T11:39:09Z

Madi at 11:34, 1 November 2017

2017-11-01T11:34:20Z

Madi: /* Report from Margherita Di Leo */

2017-11-01T11:21:56Z

Report from Margherita Di Leo

Madi at 11:21, 1 November 2017

2017-11-01T11:21:03Z

Madi: /* Selection Process */

2017-11-01T10:48:04Z

Selection Process

Madi at 07:03, 4 August 2017

2017-08-04T07:03:29Z

@@ Line 148: / Line 148: @@
 * The organisation could probably have a ''' scoring system ''' that students can see in advance to know what the key elements the organisation is looking for. This would make the process more transparent, so students know what makes a good proposal.
 * The subjective judgement of the proposal should however be private and not enclosed until the results are announced.
-What makes a good proposal?
+* What makes a good proposal?
 # Prior ''' contribution ''' (patch) or proof of concept.
 # Successful ''' interaction ''' with multiple mentors (through any channel that is used during the project later on).

@@ Line 1: / Line 1: @@
 <center>
 [[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] <font size="+3"> @ </font>
@@ Line 119: / Line 120: @@
 * How to get students work on tasks on quality assurance: make it sexy. Make task description self containing and clear.
 [[Category: Google Summer of Code]]

@@ Line 64: / Line 64: @@
 The GSoC Mentor Summit took place from Friday, Oct 13 to Sunday, Oct 15 in Sunnyvale, CA, USA. This year it gathered nearly 350 participants from all over the world. Participants include GSoC admins and mentors, 2 for each organization participating in GSoC for the current year.
-I joined a day earlier because on Friday we (6 people from different orgs) were asked to record some videos about GSoC participation for newcomers: mentors, students, etc. I was impressed by the video recording team, they guided us through the process of recording a professional video and let us discover how it really works behind the scenes.
 On Friday night the official event started with the welcome session.
-The event over the weekend was organized in parallel sessions on the model of an unconference. The idea is that, when you go to a conference, what you really take home after it are the casual chats that you have at the coffee breaks or at dinner with people that share your interests. So at the unconference, participants propose sessions of their interest and are not supposed to make a presentation, but rather sit together and speak. At Google Corners, they have rooms with white walls where you can write on, the rooms are small and cozy and in most of them you sit around an oval table.
+The event over the weekend was organized in parallel sessions on the model of an unconference. The idea is that, when you go to a conference, what you really take home, are the casual chats that you have at the coffee breaks or at dinner with people that share your interests. So at the unconference, participants propose sessions of their interest and are not supposed to make a presentation, but rather sit together and speak. At Google Corners, they have rooms with white walls where you can write on, the rooms are small and cozy and in most of them you sit around an oval table.
 The only session that requires a presentation is the one of lightning talks, where you have 3 minutes sharp to introduce one or two most relevant projects. I chose not to do present anything because as an admin I don’t feel in the position of choosing a project over the others.
 I favoured sessions where the topic was administration, umbrella organizations and most importantly Google Code-in (GCI) because we are applying this year for the first time and this seemed a great occasion to ask other organizations and gather info. Hereinafter I made a summary of the info that I collected.
 All in all, it was a great experience being there. I really think it’s useful for admins to be there and exchange information. This was my third time, and most probably my last one because also other admins should have the opportunity too.

@@ Line 63: / Line 63: @@
 == Report from Margherita Di Leo ==
-The GSoC Mentor Summit took place from Friday, Oct 13 to Sunday, Oct 15 in Sunnyvale, CA, USA.
+The GSoC Mentor Summit took place from Friday, Oct 13 to Sunday, Oct 15 in Sunnyvale, CA, USA. This year it gathered nearly 350 participants from all over the world. Participants include GSoC admins and mentors, 2 for each organization participating in GSoC for the current year.
 I joined a day earlier because on Friday we (6 people from different orgs) were asked to record some videos about GSoC participation for newcomers: mentors, students, etc. I was impressed by the video recording team, they guided us through the process of recording a professional video and let us discover how it really works behind the scenes.
 On Friday night the official event started with the welcome session.

← Older revision		Revision as of 11:39, 1 November 2017
Line 1:		Line 1:
		+	<center>
		+	[[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>
		+
		+	* Back to the main OSGeo [[Google Summer of Code 2017]] @ OSGeo wiki page.
		+
	= Google Summer of Code 2017 Mentor Summit =		= Google Summer of Code 2017 Mentor Summit =

@@ Line 70: / Line 70: @@
 * Mentor commitment: Make sure mentors understand that their presence is required during the whole period of the program (7 weeks non stop: November 28th, 2017 to January 17th, 2018) and they don’t underestimate the required time commitment. They can’t just disappear during the program. They can organize shifts during sensitive days like holidays, personal matters etc.
 * Mentors have 36 hours max to review a task when a student submit it, but preferably 24 hrs.
-Document task revisions, in order to be consistent in the evaluation.
+* Document task revisions, in order to be consistent in the evaluation.
 * Have a few mentors to clear up the queue every day
 * Encourage the students to help each other. Finalists are evaluated also on community involvement.

@@ Line 53: / Line 53: @@
 * [[user:Madi|Margherita Di Leo]]
 * [[User:Iamrohith94|Rohith Reddy]]
 [[Category: Google Summer of Code]]

@@ Line 17: / Line 17: @@
 * The call is open to hear who is interested to go. Whoever responds must COMMIT to go, otherwise you will take away the opportunity from someone else. Deadline for expression of interest is end of July. Please appoint your names in this page.
 * Selection: we agreed that we must make a (fully transparent, open) lottery. We need to find a tool that allows this. Deadline for tools proposal is by the end of July. Time is short and people need to make paperwork for VISA. Please make your proposal in this page.
-* Other requirements: the selected delegates are requested to make a report after returning home from the summit.
+* Other requirements: '''the selected delegates are requested to make a report after returning home from the summit'''.
 == Candidates ==

@@ Line 48: / Line 48: @@
 ** jmckenna's opinion: RandomPicker is exactly what we need
 * Add here your proposed tool for lottery
 [[Category: Google Summer of Code]]