How to have more SQLSaturdays?
Over the past year we've been working on the ambitious goal of building a national franchise for SQL community events, one that is based on local involvement, a repeatable process, and a reusable web site. We've had good success here in Florida (three events completed, a fourth scheduled for June here in Orlando) but so far no one has tried it outside of Florida. As we've spoken with various communities, it's more about worries than real objections, and I think they boil down to these:
Before you read further, I hope you'll follow this link to a copy of our upcoming ad in The SQL Server Standard.
If you didn't have time to read it, the short story is that we (Brian, Steve, and myself) are committing our own time and money to the first four events that run outside of Florida. We know that doesn't remove the worries entirely, but combined with our extensive planning guide and our own experience we believe we can help other communities run successful free events.
That's one step, the next is to put together a meeting of people that are really interesting in hosting a SQLSaturday. We're still looking at options, but one plan is to bring them to Orlando (has the advantage of not requiring us to lease space, and we can leverage a lot of local volunteers to join the disucssion), and the other is to meet just prior to the PASS Summit on Monday or Tuesday (has the advantage of having a lot of the right people in the right place at the right time). We've also submitted a session for the Summit about SQLSaturday, but the final schedule has not been announced yet.
What we really need are a few more success stories, and for that we need YOU! If you're interested in attending a SQLSaturday in your area, use our suggest a location link to let us see where there are clusters that we might target. If you're a user group leader or just think you have what it takes to drive one of these events, drop me a note via the blog and we'll send you some docs and arrange a call to talk through some of our experiences.
I don't know if you were going to ask or not, but we get these two questions here and there:
I hope you'll think about it, ask questions, and maybe gather a few volunteers and try it yourself. It is a lot of work, but I think you'll find it rewarding. Thanks for reading to the end!
Recently I posted about making sponsorship work to lay out some ideas for events that are seeking sponsors. My friend Shawn Weisfeld manages the Orlando .Net group and he posted his thoughts on sponsorship yesterday. The Code Camp Manifesto is where it all started and it definitely focuses not just on free, but no cash outlay. I think that's realistic if you have 5-20 people meeting, but after that I'm not sure it's practical. Orlando Code Camp has more than 400 attendees, the South Florida Code Camp more than 600. The problem isn't that those two events have strayed from the manifesto but rather than are a different animal - call it a mini conference.
On a good year perhaps 2000 people attend the PASS Summit, and maybe 11k attend Teched. I've attended at least one national conference each year since 1999, it's easy to lose sight of the fact that many people never get to go to a conference. Conferences are different from classroom training, they exist to help you explore new ideas quickly, to let you network with peers (especially valuable for us DBA's who often have no peers at work), and to just recharge. We need more of these conferences at lower prices!
I think calling it a Code Camp just lets users know that it's less formal, less likely to be perfect. Our own SQLSaturday was an attempt to be just a little more formal, to come as close to being a real conference as we could on a limited budget (about $4000) and I think we did pretty well. It's definitely important to set expectations, nothing can sour a day faster than to expect one thing and get another.
Which brings us finally to the should it be free portion of this post. I like free. It let's people come that just couldn't afford to any other way and I think they have more of a grass roots feel to them. But take SQLSaturday for example. If we had charged $20/person would they have been less happy with the event? They received coffee & doughnuts for breakfast - call that a $1.50 in value, and a nice boxed lunch from Jason's Deli - $7 value, and as much soda/water as they could drink - variable, but let's round to $1.50 to make their real received value $10. The other $10 would have paid for speaker shirts, signs, trash bags,and all the other little things needed to make things run. Would charging $20 raise expectations too high? Would it shrink attendance because many people don't want to pay anything out of their pocket?
Let's look at the choices:
I think all of those are valid choices and people looking at one of these events should really consider which model fits them and their community best.
The final point worth discussing; what happens to money left over? I think the best use is to leave it in the hands of the local user group to help subsidize bringing speakers in, but a pleasant alternative would be to donate any 'profit' to a local charity.
This topic came up during the speaker reception at the South Florida Code Camp and while I've posted here and there, it's probably worth writing down some thoughts about what events like Code Camp and SQLSaturday can do to make being a sponsor more attractive.
I know that sounds like a lot. What do you get in return?
Put as much effort into your sponsors as you do the attendees, speakers, volunteers, and site host and things will go well.