FOSS4G2008 Lessons Learned - Revision history

Wiki-Leo at 11:49, 12 February 2015

2015-02-12T11:49:38Z

2015-02-02T19:37:21Z

2011-05-25T03:25:44Z

Reverted edits by Tmitchell (Talk) to last revision by Camerons

2011-05-25T02:56:29Z

adjusting heading hierarchy

2009-02-07T10:32:12Z

Laptop Based Workshops

2009-02-04T19:52:54Z

Computers and Networks

2009-01-07T09:47:46Z

added internet traffic item

2008-12-11T14:33:37Z

Call for Papers

2008-12-11T14:28:49Z

Conference website software

2008-12-11T14:25:02Z

Submission Process

@@ Line 1: / Line 1: @@
-Back to [[Conference_Committee]]
+Back to [[Conference Committee]]
-This page is a collection of information, comments, and suggestions, based on the planning, organizing, and hosting of the FOSS4G 2008 conference. The intent is to provide a resource that can be used by organizers of future FOSS4G conferences. This is not a forum for conference attendees to comment on the conference. Use [[FOSS4G2008_Comments]] for that.
+This page is a collection of information, comments, and suggestions, based on the planning, organizing, and hosting of the FOSS4G 2008 conference. The intent is to provide a resource that can be used by organizers of future FOSS4G conferences. This is not a forum for conference attendees to comment on the conference. Use [[FOSS4G2008 Comments]] for that.
 = Bidding =
@@ Line 272: / Line 272: @@
 [[Category:FOSS4G2008]]
 [[Category:FOSS4GLessonsLearned]]

← Older revision		Revision as of 19:37, 2 February 2015
Line 273:		Line 273:
	[[Category:FOSS4G2008]]		[[Category:FOSS4G2008]]
	[[Category:FOSS4G]]		[[Category:FOSS4G]]
		+	[[Category:FOSS4GLessonsLearned]]

← Older revision		Revision as of 10:32, 7 February 2009
Line 166:		Line 166:

	Obviously a lot of the above depends on the size and type of workshop it is. A GeoDjango workshop will need to probably think more about complex software dependencies and vmware images than, say, an OpenLayers workshop (though of course the latter might also need a local WMS server if wireless is not guaranteed, at the least )		Obviously a lot of the above depends on the size and type of workshop it is. A GeoDjango workshop will need to probably think more about complex software dependencies and vmware images than, say, an OpenLayers workshop (though of course the latter might also need a local WMS server if wireless is not guaranteed, at the least )
		+
		+	See also: http://crschmidt.net/blog/326/foss4g-starts/

	== Computers and Networks ==		== Computers and Networks ==

@@ Line 154: / Line 154: @@
 There is a lot to be said for having 'clean' venues, where you have control over how things work.
 Try to encourage more interaction through careful choice and setup of venue
 == Computers and Networks ==

@@ Line 61: / Line 61: @@
 == Audio-Visual ==
 == Quirks ==
-= Accommodations =
+= Accommodation =
 = Transportation =

@@ Line 198: / Line 198: @@
 Some reviewers were confused because the 2008 conference included general GIS topics and was not restricted to open source only, and then rejected an abstract that did not mention OS. However, unless there is a joint conference again, this should not be an issue in future.
 Suggestions for 2009:
@@ Line 204: / Line 206: @@
 * Request that the authors identify one or more of the conference topics to which their submission relates. This, as well as the keywords, will help with allocating papers to sessions.
 * Allow enough time for a proper blind peer-review revision of the abstracts as well as the full papers.
 === General track ===

@@ Line 248: / Line 248: @@
 ** No list of participants easily extractable
 ** No online session navigation (as supported Indico, see www.foss4g2006.org)
 [[Category:FOSS4G2008]]
 [[Category:FOSS4G]]

@@ Line 210: / Line 210: @@
 == Submission Process ==
-At some stage the uploads stopped working, and we really had trouble in getting support on the conference system. In the end, we had to accept the full papers on the academic track via email, which obviously added a lot of work.  It also meant that we had to upload full papers manually after the conference.  Ideally, authors should be able to upload their full papers and presentations themselves, saving the track directors many hours of work.
+At some stage the OCS uploads stopped working, and we really had trouble in getting OCS support. In the end, we had to accept the full papers on the academic track via email, which obviously added a lot of work.  After the conference, we discovered that the uploads stopped working due to a file permission error on the server, and we then had to manually upload all presentations and papers. Ideally, authors should be able to upload their full papers and presentations themselves, saving the track directors many hours of work.
 Links to manuals of the conference system: