Difference between revisions of "FOSS4G 2013 Lessons Learned"
Wiki-Jo.cook (talk | contribs) |
m (→Previous Years Lessons Learned: link to Dupe) |
||
| Line 13: | Line 13: | ||
== Previous Years Lessons Learned == | == Previous Years Lessons Learned == | ||
| + | * [[FOSS4G2013 Reflections by the LOC|2013]] | ||
* [[FOSS4G 2012 Lessons Learned|2012]] | * [[FOSS4G 2012 Lessons Learned|2012]] | ||
* [[FOSS4G 2011 Lessons Learned|2011]] | * [[FOSS4G 2011 Lessons Learned|2011]] | ||
Revision as of 12:59, 22 November 2013
Workshop Booking
Workshops are limited by the size specified by the author, and also the size of the rooms available in the venue. It might be a good idea to make the importance of size more clear when asking for workshop submissions (SF). There's a juggling act to do when assigning workshops to rooms (and hence knowing the maximum number of people who can book onto it), and it's also important to consider the expected popularity of each workshop. Expect to have to move some around when bookings come in.
Dates
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.