FOSS4G 2016 Lessons Learned - Revision history

Vmische: Filling Abstract Submissions & Paper selection section

2017-03-27T13:18:04Z

Filling Abstract Submissions & Paper selection section

Tadams at 11:33, 23 September 2016

2016-09-23T11:33:50Z

Tadams at 12:31, 2 September 2016

2016-09-02T12:31:49Z

Tadams at 12:26, 2 September 2016

2016-09-02T12:26:48Z

Tadams at 12:22, 2 September 2016

2016-09-02T12:22:16Z

Tadams: /* Other side events */

2016-09-02T12:17:14Z

Other side events

Tadams at 10:54, 2 September 2016

2016-09-02T10:54:33Z

Tadams: /* Workshops */

2016-09-01T13:17:18Z

Workshops

Tadams: /* Food */

2016-09-01T13:11:53Z

Food

Tadams: /* Food */

2016-09-01T13:11:03Z

Food

← Older revision		Revision as of 13:18, 27 March 2017
Line 81:		Line 81:

	=== Abstract Submissions & Paper selection ===		=== Abstract Submissions & Paper selection ===
−	~~TBD -> link to Volkers Blogpost~~

		+	* Submission
		+	** Having a URL to the source code/project makes the review less time consuming as you wouldn't need to search for the projects if there are any doubts.
		+	** Ask the submitters to keep the abstract short. 125-150 words is a good length to make it also fast to review.
		+	* Selection:
		+	** This selection process worked well for 2014 and 2016: http://2016.foss4g.org/news-entry/abstract-review-process.html
		+	** Having about 2/3 acceptance rate seems to be a good ratio for a high quality program.
		+	** Let the program committee make the hard decisions on selecting the talks (and not the attendees with an overwhelming number of talks) and rather have less talks in parallel. Strive for quality rather than quantity.
		+	** Not all submissions are really (about) open source. Double check the projects when it doubt.
		+	* Scheduling:
		+	** If you want full flexibility, don't start selling one day passes too early as that you can't really justify to change talks between days, even if it's just a preliminary schedule.
		+	** Make the preliminary schedule as close to the final one as possible, some people plan for that day/time of the day. It's welcomed if you notify the speaker if you needed to change him/her slot for the final schedule.
		+	** Find as many session chairs as possible before the conference. If there are some missing, appoint someone of your LOC to find people to fill the gaps (someone who knows a lot of people is surely beneficial (or ask someone well connection for help finding additional session chairs)).
		+	** Print out a simple sheet for the sessions chairs explaining what they need to do (e.g. that keeping the schedule and starting on time and not earlier is also important) and place it in the rooms.
		+	** Mix academic and general track slots, don't have a dedicated room from the academic track. This way academic track talks get a higher exposure to the audience.

	=== Workshops ===		=== Workshops ===

@@ Line 45: / Line 45: @@
 * Make kind of a risk analysis, that lists the costs you have 6,3,2,1 month before the event - this shows clearly, which costs you have in the very unlikely case, you have to cancel. Comparing these costs with the number of already registered attendees will help you to sleep better ;-)
 * About Early Birdies - I just talked to Sanghee, chair of the 2015 event. In Seoul 25% of all attendees registered few days before online registration closed or did it on-site! And that's why we thought about how we can attract Early Birders with more than just a smaller price. I like the early plans from Boston attracting Early Birdies especially!
 === Registration ===
-* We are a community of late bookers, so don't get nervous if numbers are low
+* We are a community of late bookers, so don't get nervous if numbers are low at the beginning :-)
 * Maybe try to make Early Bird even more attractive than we did (we raised the difference and sent 50 EB-T-Shirts around the world)
 * Although we closed registration late (maybe too late on friday 19.8.!), still some people came and attended the conference on-site. Be prepared!
 * Having a good booking system helps really! We had the chance to rent one that was especially adapted to us
 === LOC Organization  ===
@@ Line 57: / Line 59: @@
 === Marketing ===
-TBD ?
+* We had what we called "Institutional supporters" with the deal, we name your organisation and we can use your distributor for our press releases. In my eyes that helped to reach neighboured communities!
 === Discounts ===
@@ Line 71: / Line 81: @@
 === Abstract Submissions & Paper selection ===
-TBD -> link to Colkers Blogpost
+TBD -> link to Volkers Blogpost
@@ Line 83: / Line 93: @@
 === Academic Track ===
 * need for a Student Award troubleshooter
-* we integrated AT into the regular programme instead of having one parallel track. Connects more people in our eyes.
+* we integrated AT into the regular programme instead of having one parallel track. Connected more people in our eyes.
 === Code Sprint ===
@@ Line 99: / Line 109: @@
 === Social Events ===
-TBD
+* Jeff's idea to include the GalaEvent into the conference fee took at least 700 people on the boat. What a party!
 === Other side events ===
@@ Line 106: / Line 116: @@
 === Food ===
 * Interestingly is food where we spent most of the money. Venue, Codesprint, Workshops, B2B, Gala Event.....
-* We did not request for special diets. In the end, there was 1 vegan guy out of 888 - compared to all the organisation-work to do, if offering several diets/menues, that was okay for us
+* We did not request for special diets. In the end, there was 1 vegan guy out of 889 - compared to all the organisation-work to do, if offering several diets/menues, that was okay for us
 * I guess the idea to have drinks all day was perfect (ok, Bonn was hot these days), but people like to drink when they want and not when the caterer offers. It's worth some extra money!

@@ Line 57: / Line 57: @@
 === Marketing ===
 === Discounts ===
@@ Line 69: / Line 70: @@
 * The majority did and they did a great job & were happy to have this possibility!!!
-=== Abstract Submissions  ===
+=== Abstract Submissions & Paper selection ===
 === Workshops ===
@@ Line 97: / Line 98: @@
 '''résumé''': I think good idea, especially to give student,s that can't pay the whole conference fee the chance to get an idea about FOSS4G, but planned too late. Also more promotion from Geo4All-chapter would be great. If possible, plan it from the beginning on - we started to think about, after we've noticed that some speakers cancelled their talks and we had unused session-rooms.
 === Other side events ===

@@ Line 45: / Line 45: @@
 * Make kind of a risk analysis, that lists the costs you have 6,3,2,1 month before the event - this shows clearly, which costs you have in the very unlikely case, you have to cancel. Comparing these costs with the number of already registered attendees will help you to sleep better ;-)
 * About Early Birdies - I just talked to Sanghee, chair of the 2015 event. In Seoul 25% of all attendees registered few days before online registration closed or did it on-site! And that's why we thought about how we can attract Early Birders with more than just a smaller price. I like the early plans from Boston attracting Early Birdies especially!
 === LOC Organization  ===

← Older revision		Revision as of 12:22, 2 September 2016
Line 80:		Line 80:
	=== Code Sprint ===		=== Code Sprint ===
	* I think the idea to have two extra long code sprints before and after was a good one. Of course not everywhere the possibilty we had with BaseCamp are so perfect, but I guess, if people travel, they don't mind staying longer if they have the opportunity to work with their project for longer		* I think the idea to have two extra long code sprints before and after was a good one. Of course not everywhere the possibilty we had with BaseCamp are so perfect, but I guess, if people travel, they don't mind staying longer if they have the opportunity to work with their project for longer
		+
		+	=== B2B Meeting ===
		+	* Was not there but heard all the best from the ~ 50 attendees. If so, think how you can orchestrate 25 talks from business people into one programme without the risk, that they talk too long and everyone gets bored
		+
		+	=== Student's Afternoon ===
		+	* Decision was made in late June to open the doors on friday afternoon after the last dinner for students
		+	* We also had a students session organized by Prof. Klaus Greve with 4 talks
		+	* Not much time for marketing, also we had vacations at the university, so only 9 students appeared
		+
		+	'''résumé''': I think good idea, especially to give student,s that can't pay the whole conference fee the chance to get an idea about FOSS4G, but planned too late. Also more promotion from Geo4All-chapter would be great. If possible, plan it from the beginning on - we started to think about, after we've noticed that some speakers cancelled their talks and we had unused session-rooms.

← Older revision		Revision as of 12:17, 2 September 2016
Line 83:		Line 83:

	=== Other side events ===		=== Other side events ===
		+	* We offered some side events from the official tourismus office Bonn, but had to cancel them with no bookings early. Otherwise we'd had to guarantee that we pay for the minimum attendees number and the risk was too big. Problem: We are a community of late bookers!

	=== Food ===		=== Food ===

@@ Line 18: / Line 18: @@
 === Sponsorship  ===
-* Arnulf just told me, that the 1500$ supporter package was especially created "as is", means with conference pass and is used by smaller companies - which are the ground deposit and so important for spreading the word! That's the reason, why we didn't touch it...
+* Arnulf told me, that the 1500$ supporter package was especially created "as is", means with conference pass and is used by smaller companies - which are the ground deposit and so important for spreading the word! That's the reason, why we didn't touch it...
 * We've done a very, very conservative calculation and only calculated '''40k''' sponsoring money. Of course, the more, the better, but doing that will give you a more robust view on what attendees must bring in return. Might be you should adapt your break even points or even have to rise your fees. Finally it was around €120k minus free tickets connected to the sponsorship
 * Many exhibitors asked for additional reduced and/or free tickets, which we negotiated
 * We seperated exhibition and sponsorship due to some empty big booths from Gold Sponsors in Seoul... manned booth are much more attractive for all attendees and so in general for all exhibitors ;-)
 * Exhibition costs were "as is", no extra value for us, the organizers
 === Travel Grants ===
-* The Travel Grants Program should be part of each FOSS4G. Apply for money from the board soon! Conference Committee has to define unique rules (I already requested for this)
+* The Travel Grants Program should be a fix part on every FOSS4G. Apply for money from the board soon! Conference Committee has to define unique rules (I already requested for this)
-* Should be sponsored by OSgeo and potentially the attendees. We opened a Paypal possibility, but only gathered 50€, perhaps better marketing here
+* Should be sponsored by OSgeo and potentially the attendees. We used a Paypal account, but only gathered 50€, perhaps need for better marketing here
-* We paid for ticket/overnight - paying for travel is very difficult and could hardly be managed (what if they cancel their trip a few days before? The money is lost etc.). So Travel-Grantees had to care for their travel costs on their own
+* We paid travel grantees the ticket & their overnight - paying for travels is very difficult and could hardly be managed (what if they cancel their trip a few days before? The money is lost etc.). So Travel-Grantees had to care for their travel costs on their own
-* See [[FOSS4G 2016 Travel Grants]]
+* Selection mode & more -> see [[FOSS4G 2016 Travel Grants]]
 * Make kind of a risk analysis, that lists the costs you have 6,3,2,1 month before the event - this shows clearly, which costs you have in the very unlikely case, you have to cancel. Comparing these costs with the number of already registered attendees will help you to sleep better ;-)
 * About Early Birdies - I just talked to Sanghee, chair of the 2015 event. In Seoul 25% of all attendees registered few days before online registration closed or did it on-site! And that's why we thought about how we can attract Early Birders with more than just a smaller price. I like the early plans from Boston attracting Early Birdies especially!

← Older revision		Revision as of 13:17, 1 September 2016
Line 59:		Line 59:

	=== Workshops ===		=== Workshops ===
		+	* We installed the OSGeo Live on the hardware, which was a good point, better than boot live (and even better than bring-your-own, which causes a lot of extra work for the workshop leaders)
		+	* don't expect workshop leaders to read all the information you send them. We pointed them to a weak WIFI and asked them to sent us all data/software before, but some didn't which caused some network problems, but nothing serious
		+	* plan early but also expect workshop leaders to cancel their workshops short before. So have some extra-workshops in the hind quarters
		+	* some of the workshop leaders requested tests in the venue before. If possible, make it possible ;-)
		+	* We had the strategy: "no conference-pass, no workshops" - we opened the workshops for some people that requested the weekend before the workshops actually happened. This mnakes booking the conference more attractive

	=== Academic Track ===		=== Academic Track ===

@@ Line 71: / Line 71: @@
 === Food ===
-* Provide the delegate's dietary requirements to the venues. Otherwise some delegates may not be able to eat which might make them grumpy. Especially if the food is made off-site (with no kitchen available, they can't create something off-the-cuff).
+* We did not request for special diets. In the end, there was 1 vegan guy out of 888 - compared to all the organisation-work to do, if offering several diets/menues, that was okay for us
 [[Category:FOSS4G2016]]
 [[Category:FOSS4G]]
 [[Category:FOSS4GLessonsLearned]]