Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Default Meetup Itinerary #3

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
88 changes: 88 additions & 0 deletions default_itinerary.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
# 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

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.)

* Swag giveaways

* Clean-up event space