Google Summer of Code 2013 Improvements - Revision history

Aghisla: /* This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code */

2013-09-16T12:17:39Z

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

Wiki-HamishBowman: /* This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code */

2013-04-10T09:38:09Z

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

Wiki-HamishBowman: /* This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code */

2013-04-10T09:36:38Z

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

Wiki-HamishBowman: /* This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code */

2013-04-10T09:35:01Z

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

Wiki-HamishBowman: /* This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code */

2013-04-08T23:54:43Z

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

Wiki-HamishBowman: /* This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code */

2013-04-08T23:51:44Z

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

Wiki-HamishBowman: /* This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code */

2013-04-08T23:51:03Z

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

Wiki-HamishBowman: /* This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code */

2013-04-08T23:20:55Z

This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code

Wiki-HamishBowman at 21:32, 8 April 2013

2013-04-08T21:32:24Z

Wiki-HamishBowman: init

2013-04-08T21:32:04Z

init

New page

<center>
[[Image:Gsoc-2012-logo-color.png|250px]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|200px]]
</center>

== This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code ==

* See also '''[[Google Summer of Code 2012 Improvements|suggestions from last year]]''' and others from '''[[Google Summer of Code 2011 Improvements|2011]]'''

* '''Add your idea here''': Explain it here.

[Back to [[Google Summer of Code 2013]] @ OSGeo]

[[Category:Google Summer of Code]]

← Older revision		Revision as of 12:17, 16 September 2013
Line 18:		Line 18:

	* '''Better define community bonding period''': Note this time should also be used for doing further reading and getting the full build toolchain working -- the latter being a great excuse to have a little back and forth with the community, asking for tips about the best way to configure it and send patches etc. Coding should begin at the start; the summer is too short to let 3rd week reports of "still doing some reading about it and trying to get it to build" happen. --HB		* '''Better define community bonding period''': Note this time should also be used for doing further reading and getting the full build toolchain working -- the latter being a great excuse to have a little back and forth with the community, asking for tips about the best way to configure it and send patches etc. Coding should begin at the start; the summer is too short to let 3rd week reports of "still doing some reading about it and trying to get it to build" happen. --HB
		+
		+	* '''Expand the question list for student weekly reports''': The full question list can be closer to the list shown by [http://systers.org/systers-dev/doku.php/2013_gsoc_systers_process Systers' GSoC process]:
		+	** What have you accomplished this week (list specific items accomplished)?
		+	** What issues or roadblocks have you encountered this week?
		+	** Have they been resolved, and if so, how?
		+	** Do any of the issues or roadblocks still exist and what steps have been taken to resolve them?
		+	** Is further assistance necessary to resolve existing issues?
		+	** What do you plan to accomplish next week?
		+	** How does your progress compare to your project schedule?
		+

	* '''Add your idea here''': Explain it here.		* '''Add your idea here''': Explain it here.

@@ Line 12: / Line 12: @@
 : See last year's improvement suggestions page for more details. --HB
-* '''IRC''': We've launched an OSGeo GSoC IRC channel: #osgeo-soc on the Freenode network. Should we actively promote it or try to keep things on the ML or in the open at #osgeo? Idea being to promote any tool that fosters informal peer support among the students/mentors beyond the weekly reports. --HB
+* '''IRC''': We've launched an OSGeo GSoC IRC channel: #osgeo-soc on the Freenode network. Should we actively promote it or try to keep things on the ML or in the open at #osgeo? Idea being to promote any tool that fosters informal peer support among the students/mentors beyond the weekly reports. To log it or keep things low key & off the record? (so folks are less afraid to ask silly questions) --HB
 * '''FOSS4G-NA meetup''': Anyone going to [http://foss4g-na.org/ FOSS4G-NA] in Minneapolis, May 22–24? It would be great to have a birds-of-a-feather meetup of mentors and prospective students! --HB

@@ Line 12: / Line 12: @@
 : See last year's improvement suggestions page for more details. --HB
-* '''IRC''': We've launched an OSGeo GSoC IRC channel: #osgeo-soc on the Freenode network. Should we actively promote it or try to keep things on the ML? i.e. foster informal peer support among the students/mentors beyond the weekly reports. --HB
+* '''IRC''': We've launched an OSGeo GSoC IRC channel: #osgeo-soc on the Freenode network. Should we actively promote it or try to keep things on the ML or in the open at #osgeo? Idea being to promote any tool that fosters informal peer support among the students/mentors beyond the weekly reports. --HB
 * '''FOSS4G-NA meetup''': Anyone going to [http://foss4g-na.org/ FOSS4G-NA] in Minneapolis, May 22–24? It would be great to have a birds-of-a-feather meetup of mentors and prospective students! --HB

← Older revision		Revision as of 09:35, 10 April 2013
Line 17:		Line 17:
	: ''going? let us know'' :)		: ''going? let us know'' :)

		+	* '''Better define community bonding period''': Note this time should also be used for doing further reading and getting the full build toolchain working -- the latter being a great excuse to have a little back and forth with the community, asking for tips about the best way to configure it and send patches etc. Coding should begin at the start; the summer is too short to let 3rd week reports of "still doing some reading about it and trying to get it to build" happen. --HB

	* '''Add your idea here''': Explain it here.		* '''Add your idea here''': Explain it here.

@@ Line 10: / Line 10: @@
 * '''Automated blog grind-o-matic''': Aggregate weekly blog posts at http://planet.osgeo.org
-: See last year's improvement ideas page for more details. --HB
+: See last year's improvement suggestions page for more details. --HB
 * '''IRC''': We've launched an OSGeo GSoC IRC channel: #osgeo-soc on the Freenode network. Should we actively promote it or try to keep things on the ML? i.e. foster informal peer support among the students/mentors beyond the weekly reports. --HB

@@ Line 14: / Line 14: @@
 * '''IRC''': We've launched an OSGeo GSoC IRC channel: #osgeo-soc on the Freenode network. Should we actively promote it or try to keep things on the ML? i.e. foster informal peer support among the students/mentors beyond the weekly reports. --HB
-* '''FOSS4G-NA meetup''': Who's going to [http://foss4g-na.org/ FOSS4G-NA] in Minneapolis, May 22–24? It would be great to have a birds-of-a-feather meetup of mentors and prospective students! --HB
+* '''FOSS4G-NA meetup''': Anyone going to [http://foss4g-na.org/ FOSS4G-NA] in Minneapolis, May 22–24? It would be great to have a birds-of-a-feather meetup of mentors and prospective students! --HB
-: going? let us know :)
+: ''going? let us know'' :)

← Older revision		Revision as of 23:51, 8 April 2013
Line 15:		Line 15:

	* '''FOSS4G-NA meetup''': Who's going to [http://foss4g-na.org/ FOSS4G-NA] in Minneapolis, May 22–24? It would be great to have a birds-of-a-feather meetup of mentors and prospective students! --HB		* '''FOSS4G-NA meetup''': Who's going to [http://foss4g-na.org/ FOSS4G-NA] in Minneapolis, May 22–24? It would be great to have a birds-of-a-feather meetup of mentors and prospective students! --HB
		+	: going? let us know :)

← Older revision		Revision as of 23:20, 8 April 2013
Line 7:		Line 7:

	* See also '''[[Google Summer of Code 2012 Improvements\|suggestions from last year]]''' and others from '''[[Google Summer of Code 2011 Improvements\|2011]]'''		* See also '''[[Google Summer of Code 2012 Improvements\|suggestions from last year]]''' and others from '''[[Google Summer of Code 2011 Improvements\|2011]]'''
		+
		+
		+	* '''Automated blog grind-o-matic''': Aggregate weekly blog posts at http://planet.osgeo.org
		+	: See last year's improvement ideas page for more details. --HB
		+
		+	* '''IRC''': We've launched an OSGeo GSoC IRC channel: #osgeo-soc on the Freenode network. Should we actively promote it or try to keep things on the ML? i.e. foster informal peer support among the students/mentors beyond the weekly reports. --HB
		+
		+	* '''FOSS4G-NA meetup''': Who's going to [http://foss4g-na.org/ FOSS4G-NA] in Minneapolis, May 22–24? It would be great to have a birds-of-a-feather meetup of mentors and prospective students! --HB
		+

	* '''Add your idea here''': Explain it here.		* '''Add your idea here''': Explain it here.

@@ Line 1: / Line 1: @@
 <center>
-[[Image:Gsoc-2012-logo-color.png|250px]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|200px]]
+[[Image:Gsoc-2013-logo-color.jpg|250px]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|200px]]
 </center>