Mike Moore wrote:
> I will take that one step further and say that organizing a conference by
> popular vote is less than optimal. In fact, its a total pain. I tried
it for
> the first MWRC and it didn't work for us. I was lucky enough to work with
> Pat Eyler who had a real vision of how the conference should be. In
the end
> we just executed his vision.
>
> How we work now is we have a small board of advisors to make sure we are
> making good decisions.This has worked surprisingly well for us.
>
> FWIW, YMMV, etc.
Working from the consensus of a large group of people has serious
downsides, but one upside is that the people for whom the event is
intended have both a sense of inclusion in the process and an
understanding of how decisions get made. It makes more of a community
activity. But, as Mike pointed out, the overhead can be high.
If things are not going to be decided by popular vote then whatever
means is used should at least be made public.
I don't think I ever actively participated in conferences until getting
into Ruby, and when I submitted proposals for RubyConf talks I was
pretty sure I knew who would be deciding what got accepted or not. I
didn't give it much thought until Ignite Phoenix got rolling. I had a
hand in the first event (and helped pick the talks), but after that I
was a spectator.
It occurred to me that people were being asked to take the time and
trouble to think of a talk proposal, and asked to help promote Ignite
Phoenix, but no one was told who would be judging these submissions or
by what criteria. That's a bit unfair.
When I asked about this, I was told that the selection team was kept
secret to avoid them being unduly influenced in their choices.
That's a pretty specious argument; if someone is too spineless to resist
voting for their friends, they're too spineless to resist telling their
friends they are on the event team in the first place. The better plan
is not to have team members who are so easily swayed.
(BTW, for the record, I'm on the advisory team for the upcoming MWRC.)
Now when I hear of events asking for talk proposals I want to know who
are the organizers, who's picking the talks, and what are the general
criteria for selection.
There's a bunch of stuff I want to know when asked to support an event,
if even by attending: Are talks to be recorded, and made freely
available? Who are the sponsors? Is it being used as a corporate or
product promotional event?
Bottom line: however decisions are going to be made, transparency is
important unless someone has a really good argument for keeping things
secret.
Not all of the details can be known upfront, and things can change based
on the logistics of running an event, but if you're asking people to
help out then they deserve to be kept informed.
--
James Britt
www.jamesbritt.com - Playing with Better Toys
www.ruby-doc.org - Ruby Help & Documentation
www.rubystuff.com - The Ruby Store for Ruby Stuff
www.neurogami.com - Smart application development