2014 is done and 2015 will be upon us quicker than you can imagine. To avoid the crunch of last year, I'm going to kick this off super super early - less than a week after the last event ended.

Some lessons I learned from this event.

  • The camp can (and probably should) be formulaic from a planning and execution stand point.
  • We need to set deadlines and stick to them
  • Reusing what we already have should be done when ever possible. Don't complicate things where they don't need to be complicated.

To this end, I think we should put on the same camp we did this year, next year. For sure there should be re-branding, new look and feel for the web site, different t-shirts, and a new focus for the camp.

Unless someone wants to commit super early to a change that they can own and follow through on, we should stick to what we know works.

Some things I would like to see done a bit differently.

Ticketing
I'd like to not use the issue queue for managing the Website or tasks around the event. I think I'd prefer us to use Jira, Chiliproject, or perhaps even the Git Issue system.
Timing
I'd like firm dates on tasks.
Meetings
I'd like to have monthly hangouts to discuss status on different parts of the camp.

So, without further ado, we need to start lining up volunteers. Jobs we need to sort our include the following:

  • Project Management - MatthewS
  • Venue
  • Sponsorship Coordination
  • Content Coordinator
  • Track Chairs
  • Session Selection
  • Keynotes
  • Catering / Coffee manager
  • Program and Badges
  • Stickers
  • T-shirts
  • Signage
  • Finances
  • Registration Booth
  • Design / Branding
  • Web site development
  • Parties
  • Powerstrip and extension cord provider
  • Set up / break down (power strips, tables, signage, etc.)
  • Social Media
  • Marketing
  • Customer relations
  • Trainings
  • Volunteer Wrangling

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Drupalcamp Colorado 2015 Intro » Drupalcamp Colorado 2015 Intro: Tools, Roles/responsibilities

Better title.

I vote for the git issue system.

lindsayo’s picture

lindsayo commented

I vote for the git issue system as well.

techgirlgeek’s picture

techgirlgeek commented
Issue summary: View changes
larsdesigns’s picture

larsdesigns commented

Would that be the Github issue system?

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Yeah, I was kidding since "git issues" isn't a thing. I don't actually like github. I do think it's a mistake to move elsewhere because it tends to reduce involvement, but since my involvement is likely to be minimal I'll go with the flow.

rickmanelius’s picture

rickmanelius commented

FYI. We can convert normal github issues into a Kanban board with https://waffle.io. Free for public repos.

sreynen’s picture

sreynen commented

Unless someone wants to commit super early to a change that they can own and follow through on, we should stick to what we know works.

Sounds great.

Some things I would like to see done a bit differently.

To clarify, are these things you're committing to follow through on changing? If so, are you seeking input? You listed a few options which made it feel like a vote, but you didn't actually ask for input. I have ample opinions in reserve as needed.

we need to start lining up volunteers

I volunteer to organize a beginner track. That probably needs explanation, since "beginner" has been a skill level, not a track. I'm not really suggesting we change that to call "beginner" a track this year (nor am I opposed, don't care either way). I am only suggesting someone (myself) actively plan a single session in each time slot as a schedule that would make sense for someone brand new to Drupal attending the camp. I expect that will involve at least some amount of actively recruiting speakers for pre-selected topics, a little different than our traditional session selection from submissions.

ultimateboy’s picture

ultimateboy commented

I think we should put on the same camp we did this year, next year.

One question, does this mean Denver?

sreynen’s picture

sreynen commented

The discussion at the wrapup was about doing the same camp next year at the same location in Denver, but there was also some discussion of a second event maybe happening in Boulder next year, and most people seemed interested in helping out with that as well as Denver.

matthews’s picture

matthews commented

@ultimateboy - Scott followed up on this, but yes, I think we should replicate the event pretty much identically next year. This makes even more sense given the thread you started on doing a second camp (which I think is a great idea btw).

@sreynen - I'm not interested in voting on the changes. I am very interested in hearing other perspectives and additional improvements folks might like to add to the effort. I am committed to following through on the changes - I'll pm the Denver camp again for 2015

larsdesigns’s picture

larsdesigns commented
Status: Active » Closed (fixed)