Google Summer of Code 2016 Administrative - Revision history

Maxi at 08:11, 19 April 2016

2016-04-19T08:11:59Z

Gvsig: New mentor for gvSIG project

2016-04-06T11:48:09Z

New mentor for gvSIG project

Gvsig: /* Mentors */

2016-04-05T10:59:58Z

Mentors

Neteler: +Markus Neteler

2016-04-05T10:36:03Z

+Markus Neteler

Madi: /* Tips for mentors */

2016-04-05T09:39:12Z

Tips for mentors

Madi: /* Good ideas */

2016-04-05T09:38:57Z

Good ideas

Madi: /* Good ideas */

2016-04-05T09:35:25Z

Good ideas

Madi: /* A Mentor's Responsibilities */

2016-04-05T09:33:26Z

A Mentor's Responsibilities

Wiki-Perriger: /* Mentors */

2016-03-31T01:50:24Z

Mentors

Wiki-Dburken at 14:01, 29 March 2016

2016-03-29T14:01:02Z

@@ Line 365: / Line 365: @@
 |masquesig AT gmail DOT com
 |gvSIG
+|
 |}

@@ Line 357: / Line 357: @@
 |jjdelcerro AT gvsig DOT com
 |gvSIG
 ||
 |}

@@ Line 350: / Line 350: @@
 |neteler AT osgeo DOT org
 |GRASS GIS
-||-
+|-
 |}

@@ Line 336: / Line 336: @@
+|
 |-
-|38
+|39
 |Óg
 |Crudden
@@ Line 344: / Line 344: @@
 |see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]
 |-
 |}

@@ Line 367: / Line 367: @@
 * '''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.
-* Time management tips: 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.
+* 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.
 * ...

@@ Line 366: / Line 366: @@
 === 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.
+* '''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.
-* Time management tips: 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.
+* Time management tips: 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.
 * ...

@@ Line 350: / Line 350: @@
 Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.
-Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.
+Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.
 You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.

@@ Line 335: / Line 335: @@
 |OSSIM
+|
 |-
 |}

@@ Line 327: / Line 327: @@
 |QGIS
 |QGIS Symbology Repository
 |-
 |}