Post Event Notes

[Rchristiani]

In no particular order:

• Feedback email/survey: Send out feedback email and survey after events
• Write down process for event creation (tito ticket fields): Document event details so that other people can create events and manage them if people are not available
• Twitter schedule tweets
• Reminder Email
• Auto Slack signup: System to sign people up for slack when they get a ticket
• Demo White board: A board to let people write down their names if they want to do a demo
• Theme events/different rooms : Set up events based on certain workshops(ie: express) have specific rooms for the theme.
• Slack intro of what you are working on.
• Robust Checklist: Add to it
• Slack Topic change
• Event every third Saturday of the month.
• Mentor Roll call. First on the month and one week before
• Capacity based on mentors
• If you don't have a ticket you can't come.
• Show up at 12 for mentors
• Mail chimp on website.
• Delegate event roles (ie: coffee, event space, etc)

That is all I had written down!

[brenna]

Let's all try and claim some of these & turn them into GH issues where appropriate.

I'll get started us with #26

[brenna]

Instruction type stuff can probably be added to wiki pages on this repo.

[brenna]

BAM! wiki instructions for managing the Twitter account: https://github.com/nodeschool/toronto/wiki/Managing-NodeSchool-Toronto's-Twitter-account

Let's do the same for tito & day-of event logistics

[Rchristiani]

👌

[chrismendis]

Starting a discussion on "Slack intro of what you are working on" here: #36.