FOSS4G 2013 Lessons Learned - Revision history

Jmckenna: /* Previous Years Lessons Learned */

2015-02-02T19:35:58Z

Previous Years Lessons Learned

2015-02-02T19:35:43Z

2013-12-18T18:32:41Z

refer to reflections page

2013-11-22T20:59:28Z

Previous Years Lessons Learned: link to Dupe

2013-11-20T16:31:03Z

Paper Selection Methodology

2013-11-20T16:30:13Z

Publicity

2013-11-20T16:18:18Z

Website

2013-11-20T16:16:17Z

Sponsorship

2013-05-30T08:33:54Z

Added section on comms

2013-05-30T08:26:29Z

Website

← Older revision		Revision as of 19:35, 2 February 2015
Line 26:		Line 26:
	[[Category:FOSS4G2013]]		[[Category:FOSS4G2013]]
	[[Category:FOSS4G]]		[[Category:FOSS4G]]
−	~~[[Category:FOSS4GLessonsLearned]]~~

← Older revision		Revision as of 19:35, 2 February 2015
Line 26:		Line 26:
	[[Category:FOSS4G2013]]		[[Category:FOSS4G2013]]
	[[Category:FOSS4G]]		[[Category:FOSS4G]]
		+	[[Category:FOSS4GLessonsLearned]]

← Older revision		Revision as of 18:32, 18 December 2013
Line 1:		Line 1:
		+	'' NOTE: During a wrap up meeting in November after the event, the local committee members compiled many thoughts and recommendations: Please see [[FOSS4G2013 Reflections by the LOC]] ''
		+
	==Workshop Booking==		==Workshop Booking==

@@ Line 13: / Line 13: @@
 == Previous Years Lessons Learned  ==
 * [[FOSS4G 2012 Lessons Learned|2012]]
 * [[FOSS4G 2011 Lessons Learned|2011]]

← Older revision		Revision as of 16:31, 20 November 2013
Line 1:		Line 1:
−	~~==Paper Selection Methodology==~~
−
−	The OSGeo community is very passionate about openness, so the methodology needs to be made as explicit and open as possible. Where additional filtering on top of the community vote is required (which it invariably is) then this needs to be explained clearly in the wiki. There probably ought to be an established methodology for doing this, which should be recorded in the [[FOSS4G Cookbook]].
−
	==Workshop Booking==		==Workshop Booking==

← Older revision		Revision as of 16:30, 20 November 2013
Line 1:		Line 1:
−	~~==Publicity==~~
−
−	~~We've used Lanyrd to publicise the event alongside the "usual" channels, and also Eventbrite for dealing with the free hackathon registration.~~
−
	==Paper Selection Methodology==		==Paper Selection Methodology==

← Older revision		Revision as of 16:18, 20 November 2013
Line 1:		Line 1:
−	~~==Website==~~
−
−	A submission notification should be provided within the service for submitting abstract, workshop, etc. An automatic reply mail would do the trick. We did have a section on the web page leading to the submission section that said people wouldn't receive confirmation, but either they missed this or wanted to check anyway, so it ended up causing more work.
−
−	A lot of effort went into building the website (WordPress with a conference plugin?) and a custom theme and then writing some custom stuff for the provisional program, tag filtering and the timetabling of presentations and workshops. Perhaps these modules could be re-used to save other the same effort.
−
	==Publicity==		==Publicity==

← Older revision		Revision as of 16:16, 20 November 2013
Line 1:		Line 1:
−	~~==Sponsorship==~~
−
−	This year we had a "supporter" sponsorship level, which was aimed at those companies who would not want a stand, but would want some minor branding on the website and at the event. This was very popular and we'd recommend it to future organisers.
−
	==Website==		==Website==

← Older revision		Revision as of 08:33, 30 May 2013
Line 24:		Line 24:

	Ensure the program is out before the end of the early bird deadline as people may wish to choose which day(s) they attend on the basis of the program.		Ensure the program is out before the end of the early bird deadline as people may wish to choose which day(s) they attend on the basis of the program.
		+
		+	==Communications==
		+
		+	'''You cannot please the whole community all of the time!''' so don't try. The mailing lists can be pretty critical and trying to patiently explain each decision may sometimes just stir up more criticism, avoid getting into public mail disputes on the list. It would be good to have more Board participation on some of the contentious topics.

	== Previous Years Lessons Learned ==		== Previous Years Lessons Learned ==

@@ Line 7: / Line 7: @@
 A submission notification should be provided within the service for submitting abstract, workshop, etc. An automatic reply mail would do the trick. We did have a section on the web page leading to the submission section that said people wouldn't receive confirmation, but either they missed this or wanted to check anyway, so it ended up causing more work.
-A lot of effort went into building the website (WordPress with a conference plugin(?) and a custom theme and then writing some custom stuff for the provisional program, tag filtering and the timetabling of presentations and workshops. Perhaps these modules could be re-used to save other the same effort.
+A lot of effort went into building the website (WordPress with a conference plugin?) and a custom theme and then writing some custom stuff for the provisional program, tag filtering and the timetabling of presentations and workshops. Perhaps these modules could be re-used to save other the same effort.
 ==Publicity==