Code Sprint Guidelines - Revision history

Delawen at 08:23, 25 August 2019

2019-08-25T08:23:02Z

Delawen: Redirected page to Archived

2019-08-25T07:41:15Z

Redirected page to Archived

Neteler at 19:50, 29 August 2016

2016-08-29T19:50:44Z

Aghisla: added Board category and Board-approved disclaimer on top

2013-11-29T09:31:31Z

added Board category and Board-approved disclaimer on top

Wiki-Camerons at 20:43, 17 October 2013

2013-10-17T20:43:58Z

Wiki-Camerons at 20:39, 17 October 2013

2013-10-17T20:39:07Z

Jmckenna at 11:04, 22 September 2013

2013-09-22T11:04:38Z

Jmckenna at 10:49, 22 September 2013

2013-09-22T10:49:27Z

Jmckenna: change name of C tribe / NA sprint

2013-09-22T10:06:43Z

change name of C tribe / NA sprint

Aghisla: /* Submission of a funding request */

2013-09-22T09:28:25Z

Submission of a funding request

← Older revision		Revision as of 08:23, 25 August 2019
Line 1:		Line 1:
	#REDIRECT [[Archived]]		#REDIRECT [[Archived]]
		+
		+	Latest guidance can be found on https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidence.pdf

	* This [http://wiki.osgeo.org/index.php?title=Code_Sprint_Guidelines&oldid=74616 article] has been approved by the OSGeo Board of Directors in their 2013-10-17 [[Board_Meeting_2013-10-17\|Board Meeting]].		* This [http://wiki.osgeo.org/index.php?title=Code_Sprint_Guidelines&oldid=74616 article] has been approved by the OSGeo Board of Directors in their 2013-10-17 [[Board_Meeting_2013-10-17\|Board Meeting]].

← Older revision		Revision as of 07:41, 25 August 2019
Line 1:		Line 1:
		+	#REDIRECT [[Archived]]
		+
	* This [http://wiki.osgeo.org/index.php?title=Code_Sprint_Guidelines&oldid=74616 article] has been approved by the OSGeo Board of Directors in their 2013-10-17 [[Board_Meeting_2013-10-17\|Board Meeting]].		* This [http://wiki.osgeo.org/index.php?title=Code_Sprint_Guidelines&oldid=74616 article] has been approved by the OSGeo Board of Directors in their 2013-10-17 [[Board_Meeting_2013-10-17\|Board Meeting]].
	* Please add comments and suggestions in the associated [[Talk:Code_Sprint_Guidelines\|Talk page]].		* Please add comments and suggestions in the associated [[Talk:Code_Sprint_Guidelines\|Talk page]].

← Older revision		Revision as of 19:50, 29 August 2016
Line 57:		Line 57:
	[[Category:Code_Sprints]]		[[Category:Code_Sprints]]
	[[Category:Board]]		[[Category:Board]]
		+	[[Category:Budget]]
		+	[[Category:Finance]]

← Older revision		Revision as of 09:31, 29 November 2013
Line 1:		Line 1:
		+	* This [http://wiki.osgeo.org/index.php?title=Code_Sprint_Guidelines&oldid=74616 article] has been approved by the OSGeo Board of Directors in their 2013-10-17 [[Board_Meeting_2013-10-17\|Board Meeting]].
		+	* Please add comments and suggestions in the associated [[Talk:Code_Sprint_Guidelines\|Talk page]].
		+	----
		+
	A codesprint is an in-person gathering of developers for doing some serious coding, writing documentation, and having face-to-face project collaboration. (It is not aimed at training, presentations, workshops, etc.)		A codesprint is an in-person gathering of developers for doing some serious coding, writing documentation, and having face-to-face project collaboration. (It is not aimed at training, presentations, workshops, etc.)

Line 52:		Line 56:

	[[Category:Code_Sprints]]		[[Category:Code_Sprints]]
		+	[[Category:Board]]

← Older revision		Revision as of 20:43, 17 October 2013
Line 44:		Line 44:

	= OSGeo Sponsorship Criteria =		= OSGeo Sponsorship Criteria =
−
−	~~''- Draft proposal -''~~

	When deciding to support a sprint, OSGeo should follow these guidelines:		When deciding to support a sprint, OSGeo should follow these guidelines:

@@ Line 1: / Line 1: @@
 A codesprint is an in-person gathering of developers for doing some serious coding, writing documentation, and having face-to-face project collaboration. (It is not aimed at training, presentations, workshops, etc.)
-The OSGeo community has two annual "big" sprints (annual, multiproject, multiday events of more than 20 people): the [[:Category: Bolsena|Bolsena Sprint]] and the [[:Category: C Tribe Code Sprint|C Tribe Sprint]]. A number of [[:Category: Code Sprints|project-oriented sprints]] also occur, such as the one-day sprint associated with FOSS4G conferences, single-project sprints such as have been held for GRASS GIS, QGIS and uDig, and very regional (chapter-level) sprints.
+By 2013, The OSGeo community has two annual "big" sprints (annual, multiproject, multiday events of more than 20 people): the [[:Category: Bolsena|Bolsena Sprint]] and the [[:Category: C Tribe Code Sprint|C Tribe Sprint]]. A number of [[:Category: Code Sprints|project-oriented sprints]] also occur, such as the one-day sprint associated with FOSS4G conferences, single-project sprints such as have been held for GRASS GIS, QGIS and uDig, and very regional (chapter-level) sprints.
-Codesprints are clearly within the scope of OSGeo's mission, and so the Foundation should in general support them. This page provides some guidelines for deciding whether a given sprint should be supported, and if so in what fashion.
+Codesprints are clearly within the scope of OSGeo's mission, and the OSGeo Foundation supports them. This page provides some guidelines for deciding whether a given sprint should be supported, and if so in what fashion.
 = Sprint Info Required =
@@ Line 31: / Line 29: @@
 *what is the expected cost per attendee, for travel, lodging, and food?
 *what is the expected cost for the venue (such as conference room, wifi support, snacks, etc)?
 '''Profit / Loss / Risk'''
@@ Line 45: / Line 41: @@
 # Board adds a "Sprint support" agenda item for upcoming Board meeting, and invites sprint organiser(s) to join the meeting and provide clarification where needed.
 # Board votes on the funding request.
-# Upon approval, and within one month from the end of the sprint, sprint organisers provide a publicly accessible summary budget of the actual expenses. A more detailed budget shall be made available to OSGeo Treasurer. Would the final budget not be available to OSGeo, future fund requests will be taken on hold until final budget publication.
+# Upon approval, and within one month from the end of the sprint, sprint organisers provide a publicly accessible summary budget of the actual expenses. A more detailed budget shall be made available to OSGeo Treasurer. Should the final budget not be available to OSGeo, future fund requests will be with held until final budget publication.
 = OSGeo Sponsorship Criteria  =

@@ Line 3: / Line 3: @@
 A codesprint is an in-person gathering of developers for doing some serious coding, writing documentation, and having face-to-face project collaboration. (It is not aimed at training, presentations, workshops, etc.)
-The OSGeo community has two annual "big" sprints (annual, multiproject, multiday events of more than 20 people): the Bolsena Sprint and the C Tribe Sprint. A number of [[:Category: Code Sprints|project-oriented sprints]] also occur, such as the one-day sprint associated with FOSS4G conferences, single-project sprints such as have been held for GRASS GIS, QGIS and uDig, and very regional (chapter-level) sprints.
+The OSGeo community has two annual "big" sprints (annual, multiproject, multiday events of more than 20 people): the Bolsena Sprint and the [[:Category: C Tribe Code Sprint|C Tribe Sprint]]. A number of [[:Category: Code Sprints|project-oriented sprints]] also occur, such as the one-day sprint associated with FOSS4G conferences, single-project sprints such as have been held for GRASS GIS, QGIS and uDig, and very regional (chapter-level) sprints.
 Codesprints are clearly within the scope of OSGeo's mission, and so the Foundation should in general support them. This page provides some guidelines for deciding whether a given sprint should be supported, and if so in what fashion.

@@ Line 42: / Line 42: @@
 '''Proposed workflow:'''
-# The sprint organisers fill out above questionnaire and submit it to Board list.
+# Sprint organisers fill out the questionnaire above and submit it to Board list.
 # Board adds a "Sprint support" agenda item for upcoming Board meeting, and invites sprint organiser(s) to join the meeting and provide clarification where needed.
 # Board votes on the funding request.
-# Upon approval of the requested OSGeo funds, and within one month from the end of the sprint, sprint organisers provide a publicly accessible summary budget of the actual expenses. A more detailed budget shall be made available to OSGeo Treasurer. Would the final budget not be available to OSGeo, future fund requests will be taken on hold until final budget publication.
+# Upon approval, and within one month from the end of the sprint, sprint organisers provide a publicly accessible summary budget of the actual expenses. A more detailed budget shall be made available to OSGeo Treasurer. Would the final budget not be available to OSGeo, future fund requests will be taken on hold until final budget publication.
 = OSGeo Sponsorship Criteria  =