|
|
* Set up earlier in the morning (night before?)
|
|
|
* Coffee available all day even if for purchase
|
|
|
* More organized support desk / community bar
|
|
|
* More "block and tackle" type sessions
|
|
|
* Communicate about parking at conference center
|
|
|
* Simple map for parking
|
|
|
* BOF sessions at lunch tables?
|
|
|
* Keynote to start the day
|
|
|
* More lighting talks
|
|
|
* Take the picture at lunch
|
|
|
* Define photos we want to make sure we get ahead of time
|
|
|
* Ride share options? Promote in advance?
|
|
|
* Session on the community (how to get involved) and community tools (Mattermost, StackExchange, GitLab, Jira, Website, etc.)
|
|
|
* Session on release management
|
|
|
* look at what we can do to improve attendance at after-party
|
|
|
* Sprint immediately after CiviCamp
|
|
|
* We need an packet / envelope for each session monitor that includes what they should say in the beginning - the speaker's bio, the session description, handing out the surveys, collecting the surveys (include large envelope), that they should facilitate the Q&A, etc.,
|
|
|
* Have the after-camp survey cued up and ready to go before CiviCamp
|
|
|
* look for more "out of ecosystem" sponsors
|
|
|
* Have a laptop available for last minute registrations
|
|
|
* Promote on meetup and more varied channels
|
|
|
* Define and publicize the sessions much earlier
|
|
|
* Have a designated marketing / social media person leading up to the event and on the day of |
|
|
\ No newline at end of file |