From 9d04b251f85029f2cfe31eed7ae291cfe8927316 Mon Sep 17 00:00:00 2001 From: Derek Lindahl Date: Wed, 21 Jan 2015 21:28:40 -0800 Subject: [PATCH 1/2] Add initial default meetup itinerary --- default_itinerary.md | 77 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 default_itinerary.md diff --git a/default_itinerary.md b/default_itinerary.md new file mode 100644 index 0000000..05115f9 --- /dev/null +++ b/default_itinerary.md @@ -0,0 +1,77 @@ +# Default Meetup Itinerary + +###### 6:00 - Meetup Preparation + +* Setup event space (chairs, swag, food, etc.) + +* Welcome speakers + + Ensure speakers have arrived, are parked, settled, laptops are charged and + work with the projector. + + Ensure speakers are aware of the Code of Conduct and agree not to violate it. + +* Prepare first speaker (laptop charged, slides ready to run, etc.) + +###### 6:30 - Meetup Starts + +* General Welcome + + Your typical "Hi, and welcome" spiel + + Communicate the presence of the Code of Conduct (tl;dr is fine) and address + how attendees can report violations by reporting it to the staff which can + be identified through... + +* Staff Introductions + + So that everyone attending knows who to go to with questions or report a + problem, each staff member should give a friendly introduction that includes + their name, location (East Sac, Rocklin, Elk Grove, etc.), and something + unique about themselves (while stay in context of JS). + + This also sets the table to ask attendees to do the same in... + +* Attendee Introductions + + We are hear to build a community and too many other groups don't give an + opportunity for attendees to meet each other. Following the same format as + the staff, give each attendee a chance to introduce themselves to the group. + + No pressure here, though. If someone is shy and wants to be skipped, move + quickly on to the next person. + +* Sponsor Introductions + + Provide 2-min platform for sponsors to address attendees. Wrap up by thanking + the sponsor and + +###### 7:00 - First Talk + +* First talk begins + +###### 7:25 - Second Talk Preparation + +* Prepare second speaker (laptop charged, slides ready to run, etc.) + +###### 7:30 - Second Talk + +* Second talk begins + +###### 7:55 - Third Talk Preparation + +* Prepare third speaker (laptop charged, slides ready to run, etc.) + +###### 8:00 - Third Talk + +* Third talk begins + +###### 8:30 - Meetup Ends + +* Closing remarks (next meetup date, topic, thank sponsors, etc.) + +* Community cross-promotion (Angular, Famous, GDG, etc.) + +* Swag giveaways + +* Clean-up event space From a33eb0f898394c5ddabe5f1fcf9701dc8d071df7 Mon Sep 17 00:00:00 2001 From: Derek Lindahl Date: Wed, 21 Jan 2015 21:33:18 -0800 Subject: [PATCH 2/2] Add blurb about Module of the Month --- default_itinerary.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/default_itinerary.md b/default_itinerary.md index 05115f9..839189e 100644 --- a/default_itinerary.md +++ b/default_itinerary.md @@ -68,7 +68,18 @@ ###### 8:30 - Meetup Ends -* Closing remarks (next meetup date, topic, thank sponsors, etc.) +* Closing remarks + + Announce next meetup date, topic, thank sponsors, etc. + +* Module of the Month + + I think it would be cool to highlight a neat module that we find useful or + unique. Some great sources of ideas include DailyJS. + + Not only does this expose attendees to cool modules, but it can also highlight + the existence of NPM/Bower and the power of open source to our beginner + attendees. * Community cross-promotion (Angular, Famous, GDG, etc.)