Google Summer of Code Recommendations for Students - Revision history

Strk: /* How to get in contact via IRC */ replace old section with a link to IRC page

2023-03-09T10:29:31Z

How to get in contact via IRC: replace old section with a link to IRC page

Wenzeslaus: /* 6. GSoC participation */ participated to/in GSoC

2021-03-30T19:00:23Z

6. GSoC participation: participated to/in GSoC

RajatShinde: Making this a generalized page for GSoC Reccomendations

2021-02-05T05:09:41Z

Making this a generalized page for GSoC Reccomendations

Madi: /* Weekly reports */

2019-06-03T07:01:01Z

Weekly reports

Madi: /* Weekly reports */

2019-06-03T07:00:03Z

Weekly reports

Madi at 06:58, 3 June 2019

2019-06-03T06:58:22Z

Madi: /* 3. Timeline */

2019-04-05T15:10:31Z

3. Timeline

Madi: /* 6. GSoC participation */

2019-04-04T07:14:37Z

6. GSoC participation

Madi: /* 3. Timeline */

2019-04-04T07:10:10Z

3. Timeline

Madi: /* 3. Timeline */

2019-04-04T07:05:34Z

3. Timeline

@@ Line 185: / Line 185: @@
 == How to get in contact via IRC ==
-Primary channel:
+See [[IRC]] page
 [[Category: Google Summer of Code]]

@@ Line 114: / Line 114: @@
 ==== 6. GSoC participation ====
-* Have you participated to GSoC before?
+* Have you participated in GSoC before?
 * How many times, which year, which project?
 * Have you applied but were not selected? When?

@@ Line 3: / Line 3: @@
 [[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
 </center>
 == How to get in contact with your potential mentors ==

← Older revision		Revision as of 07:01, 3 June 2019
Line 161:		Line 161:

	If you want, feel free to expand your report, however this is the minimum required.		If you want, feel free to expand your report, however this is the minimum required.
−
−	~~Please explicitly mention your project in the subject and in the introduction to the e-mail.~~

	'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and especially if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, definitely tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)		'''IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME''', if you don't send this email your mentors will start to get twitchy, and especially if they don't get any responses to their emails / don't see you on IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's OK. Just tell us about it up front, be honest, and we'll work around it. If you don't know how to proceed and your mentor isn't answering, definitely tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

@@ Line 151: / Line 151: @@
 === Weekly reports ===
-Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, your weekly progress report. You are requested to send the report  mail even if you didn't code because of exams or holidays, or any other reason. The report should to contain the title of the project in the subject, the link to your wiki page, the link to the public repository of your weekly commits and at least the answers to these 3 questions:
+Every week, by Sunday, we expect to see your weekly progress report posted to the soc@osgeo and the developer mailing list of your project. You are requested to send the report even if you didn't code because of exams or holidays, or any other reason. The report should to contain the title of the project in the subject, the link to your wiki page, the link to the public repository of your weekly commits and at least the answers to these 3 questions:
 # What did you get done this week?

@@ Line 151: / Line 151: @@
 === Weekly reports ===
-Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, that at least answers the following questions:
+Every week, by Sunday, we expect to see a report posted to the soc@osgeo and the developer mailing list of your project, your weekly progress report. You are requested to send the report  mail even if you didn't code because of exams or holidays, or any other reason. The report should to contain the title of the project in the subject, the link to your wiki page, the link to the public repository of your weekly commits and at least the answers to these 3 questions:
 # What did you get done this week?
@@ Line 160: / Line 160: @@
 [http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process].
-If you want, feel free to write *more*. But three sentences is the bare minimum.
+If you want, feel free to expand your report, however this is the minimum required.
 Please explicitly mention your project in the subject and in the introduction to the e-mail.

@@ Line 106: / Line 106: @@
 * The workload should be split in weekly chunks.
 * Your timeline should contain actual dates, not "week 1", "week 2", etc.
-* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
+* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, familiarize with the code base and with the mentors, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
 * Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
 * Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

@@ Line 124: / Line 124: @@
 * How many times, which year, which project?
 * Have you applied but were not selected? When?
-* Have you submitted/will you submit another proposal for this year's GSoC to a different org?
+* Have you submitted/will you submit another proposal for this year's GSoC to a different org? Which one?
 == What to expect after application ==

@@ Line 104: / Line 104: @@
 ==== 3. Timeline ====
 * Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
 * Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
 * Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?