Google Summer of Code Application 2013 - Revision history

Aghisla: /* Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. */

2013-03-28T09:20:04Z

Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here.

Aghisla: /* Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. */

2013-03-28T09:03:03Z

Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here.

Aghisla: /* What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes? */

2013-03-28T09:00:49Z

What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?

Aghisla: /* What steps will you take to encourage students to interact with your project's community before and during the program? */

2013-03-28T09:00:04Z

What steps will you take to encourage students to interact with your project's community before and during the program?

Aghisla: /* What is your plan for dealing with disappearing mentors? */

2013-03-28T08:56:11Z

What is your plan for dealing with disappearing mentors?

Aghisla: /* What is your plan for dealing with disappearing students? */

2013-03-28T08:54:45Z

What is your plan for dealing with disappearing students?

Aghisla: /* What criteria did you use to select your mentors for this year's program? Please be as specific as possible. */

2013-03-28T08:53:33Z

What criteria did you use to select your mentors for this year's program? Please be as specific as possible.

Aghisla: /* Why is your organization applying to participate in GSoC 2013? What do you hope to gain by participating? */

2013-03-28T08:52:31Z

Why is your organization applying to participate in GSoC 2013? What do you hope to gain by participating?

Aghisla at 08:51, 28 March 2013

2013-03-28T08:51:27Z

Wiki-HamishBowman: /* What will you do to encourage / sp

2013-03-28T05:00:22Z

/* What will you do to encourage / sp

@@ Line 273: / Line 273: @@
 === Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===
-This year we did not receive vouching requests.
+No text - because this year we did not receive any vouching request.
 Still, as an umbrella organization we are fundamentally a conglomerate of small(er) organizations and so are well experienced in helping smaller mentoring teams. We have been happy to mentor-mentor small orgs in the past when they've approached us, each year taking in a few in-the-same-field projects who were not technically members of our Foundation but who otherwise would have missed out.

@@ Line 272: / Line 272: @@
 === Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here. ===
-As an umbrella organization we are fundamentally a conglomerate of small(er) organizations and so are well experienced in helping smaller mentoring teams. We have been happy to mentor-mentor small orgs in the past when they've approached us, each year taking in a few in-the-same-field projects who were not technically members of our Foundation but who otherwise would have missed out.
+This year we did not receive vouching requests.
 <!--

← Older revision		Revision as of 09:00, 28 March 2013
Line 261:		Line 261:

	=== What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes? ===		=== What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes? ===
−
−	~~'''[provisional]'''~~

	* Socially it's a nice place to be: As a large and mature FOSS organization with a large academic presence we have had a lot of success fostering a professional and friendly community environment.		* Socially it's a nice place to be: As a large and mature FOSS organization with a large academic presence we have had a lot of success fostering a professional and friendly community environment.

@@ Line 251: / Line 251: @@
 === What steps will you take to encourage students to interact with your project's community before and during the program? ===
+(required)
 The steps taken depend on the individual projects. As an example, in previous years we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.
@@ Line 259: / Line 258: @@
 We had hoped to encourage projects and students to get together during our large omnibus FOSS4G conference in May, but unfortunately the timing is out by a few days with respect to the accepted-students announcement and we will have to concentrate on smaller individual project code-sprints instead for in-person meet-ups. For example, in 2011 and 2012 we had good success with this with students introduced to the development community and talking about their projects early in the summer:
-http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Prague_2011 <br>
+http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Prague_2011 and http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Prague_2012
 === What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes? ===

← Older revision		Revision as of 08:56, 28 March 2013
Line 244:		Line 244:

	=== What is your plan for dealing with disappearing mentors? ===		=== What is your plan for dealing with disappearing mentors? ===
−
−	~~'''[provisional]'''~~

	<!-- Violence.^w -->		<!-- Violence.^w -->

@@ Line 232: / Line 232: @@
 === What is your plan for dealing with disappearing students? ===
 	(required)
-'''[provisional]'''
 In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project, and require a timeline (including exams and vacations to work around) as part of the application.

@@ Line 225: / Line 225: @@
 === What criteria did you use to select your mentors for this year's program? Please be as specific as possible. ===
 (required)
-'''[provisional]'''
 The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people she trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. Backup mentors (mentors in training) are chosen by the member-project dev communities.

← Older revision		Revision as of 08:52, 28 March 2013
Line 198:		Line 198:
	(required)		(required)

−	~~'''[provisional]'''~~
	We hope to get more students excited about both open source and geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.		We hope to get more students excited about both open source and geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

@@ Line 8: / Line 8: @@
 == Application Deadline ==
-Status: '''''Not yet applied'''''
+Status: '''''Applied with the text below'''''
 : Timeline: http://www.google-melange.com/gsoc/events/google/gsoc2013
@@ Line 23: / Line 23: @@
 == Pending ==
 == New ==
@@ Line 147: / Line 143: @@
 : 20/22
 OSGeo participated in 2012, with 20 of 22 students completing the summer.
 <!-- After initial slot assignment we gave z slots to other orgs, and gave z' slots back into the general pool. -->
-We provided GSoC-specific umbrella support for two smaller projects from outside of our Foundation. <!-- pgRouting and Ofero Toolbox -->
+We provided GSoC-specific umbrella support for two smaller projects from outside of our Foundation. <!-- pgRouting and Orfeo Toolbox -->
 Successes: All in all our students were great and a lot of good work was completed -- perhaps the least remarkable-sounding but most important success we had is how smoothly everything ran in spite of handling our largest number of students yet.

@@ Line 276: / Line 276: @@
 * Socially it's a nice place to be: As a large and mature FOSS organization with a large academic presence we have had a lot of success fostering a professional and friendly community environment.
 * Recognition: It is important to us that students feel they are part of the project and see their hard work appreciated.
-* Results: By encoraging ongoing community engagement during the student-mentor period we hope to knit the student into the project over the summer, to avoid the situation of having the student-mentor interaction happening in private and the code branch languishing without buy-in from the greater dev community.
+* Results: By encouraging ongoing community engagement during the student-mentor period we hope to knit the student into the project over the summer, to avoid the situation of having the student-mentor interaction happening in private and the code branch languishing without buy-in from the greater dev community.
 * Clear expectations: This year we are again asking the student to discuss the time after the summer in their initial application.