Okay, so in my usual enthusiasm, I got ahead of myself and said "ohai,
@seleniumconf" Wednesday on Twitter. In so doing, I did this in
backwards order and inadvertently telegraphed an inaccurate picture.
What Sauce Labs should have done and what I intended to do, is first
discuss this on the Selenium Developers mailing list. Just as the
dozen or so San Francisco Selenium Meetup events we’ve sponsored over
the past 18 months have clearly been community events, so will the
Selenium Conference clearly be a community event. From the start, we
plan and want the voice of the community to be heard and embraced by
this conference.
As we’re fond of saying at Sauce, it’s okay to be wrong, not okay to
stay wrong. So here we go: Let's chat...
The origins of the idea for a Selenium Conference:
Though the project is now over 6 years old, we've yet to do a proper
in-person community event to talk just about Selenium for an extended
period of time. When I've met up with fellow Selenium committers, the
idea of doing a real conference has come up often. The one-evening
meetups we have sponsored at LinkedIn, Mozilla, Google and Trulia
among others are great fun, but it's time we do more. Up to now,
planning a Selenium conference has just been idle beer banter. But now
is the time to put down the beers and do this for real. As part of the
communication issue described by Patrick, I believe face to face would
encourage better and more transparent communication amongst everyone
in the community.
First steps towards planning a Selenium conference:
* Pick a date
* Pick a city
* Pick a venue
* Register a domain name and create a twitter account. <-- DONE!
* Talk about it with the world.
* Get more people involved.
As you can see, we're just getting started. The folks I work with at
Sauce (Ashley Wilson, Jeff Goldsmith, and Adam Christian) have done
some of the initial work on the first four items. So far, we've
narrowed down some candidate dates: April 1-3, March 4-6, March 18-20.
The initial idea is for official festivities to be a Saturday through
1/2 day Sunday, with an unofficial kick-off mixer Friday night. We
have found two venues for April 1-3 in San Francisco, that don't seem
to conflict with other conferences.
Crunching the numbers, there are three great candidate cities for
hosting the conference:
* San Francisco
* London
* New York City
Not coincidentally, that is the ranking of cities by "highest
concentrations of people talking about and doing things with
Selenium". (My personal favorite would be Chicago, the birthplace of
Selenium, but as Chicago Cubs fans say, "there's always next year".)
I'd like to clear some things up:
* Anyone who wants to sponsor can, anyone who wants to help can.
* Sauce Labs is putting in the legwork to make this conference happen,
but it's not “the Sauce Labs Conference,” it’s “The Selenium
Conference” and it will look and feel like that. It's _your_
conference.
There will be two groups to make a Selenium conference happen. The
"Workhorse Committee" and the "Advisory Committee". The Workhorse
Committee is an apt name, they will do the stuff that needs doing and
ensure it gets done. This is not a glamorous post; it will be a grind,
but there's a bouquet of roses waiting for them at the end. (I'll pay
for the roses.) The other committee is the Advisory Committee, anyone
who has a stake in how this thing should be run, should be on this
list. We'll probably set up two mailing lists, one for each group, and
it'll be up to the groups to figure out how they operate between now
and the conference.
Workhorse Committee:
* Jason Huggins (Sauce Labs)
* Jeff Goldsmith (Sauce Labs)
* Ashley Wilson (Sauce Labs)
* Adam Christian (Sauce Labs)
Advisory Committee:
* Jason Huggins (Sauce Labs)
* Patrick Lightbody (BrowserMob)
* Simon Stewart (Google)
* Adam Goucher (Element 34, and occasional Sauce Labs covert ops)
* Adam Christian (Sauce Labs)
* Kevin Menard (Mogotest)
* Dave Hunt (Mozilla)
* David Burns (Mozilla)
These are my suggestions for Workhorse and Advisory committees. If
you're on the list, and don't want to be, speak up. Or, if your name
is *not* on this list, and you want it added, again, speak up.
Committees are great, but in the interest of ensuring this conference
is a success, we also need a single point of responsibility.
Delegation fails sometimes. So I'm listing a single name as the "if
you want stuff fixed/done/ideaified, go to" person. I'm that person.
I'm _not_ the Benevolent Dictator For Life for Selenium, but I am the
Benevolent Dictator For This Conference. Send me your input. I’m
listening.
Again, this is a community event. Sauce Labs and I are facilitating
this to ensure the event happens for the benefit of the community in
the most awesomest way it can. We can make the financial commitment to
make this real - sponsorships and tickets will fund the venue and
other logistics, and any extra proceeds will go back to the Selenium
project.
So chime in everyone.
Cheers,
\ hugs /
(aka "Jason Huggins")
email:
hu...@saucelabs.com
twitter: @hugs