Launching a new Devopsdays Chattanooga event
Overview
Before you dive into running the event, it's recommended that you start here. The goal of this runbook is to provide you with all the knowledge needed to launch a devopsdays event.
Getting started
Organizing roles and committees
| Role | Description |
|---|---|
| Organizing Lead | This individual essentially functions as the project manager for the event |
| Committee co-chair | Committee co-chairs are responsible for executing tasks within a functional area (e.g., technology, volunteers) |
| Committee name | Description |
|---|---|
| Finance | How we fund, spend and account money for the conference |
| Locals | How we do partner with local vendors |
| Marketing | How we market the event |
| Registration | How we handle registration |
| Speakers | How we select speakers |
| Sponsors | How we partner with sponsors |
| Swag | How we get conference swag |
| Technology | How we administer the tech Devopsdays Chattanooga uses |
| Volunteers | How we partner with volunteers |
Event "order of operations"
There's an order of operations that has to happen in sequence in order to start the process for launching an event:
- An initial organizer communication to determine who will be involved
- An initial organizer meeting to start divvying up responsibilities
- Technology committee members set up and configure:
- Devopsdays site
- Trello board
- Google Drive folder
- Work with the Devopsdays Core Team to add any new members to the email distribution list & global Slack channel
- Establish a regular meeting cadence
Once these initial tasks are complete, everything generally flows along with the timeline in the "Dates & deadlines" doc.
note
The more that you can frontload tasks and ensure that they're in Trello, the easier it is later in the event planning process.