[UPDATE] RubyConf 2006 registration pre-info

[dblack]

Hi --

Here's the current status of RubyConf registration:

My current plan, barring unforeseen whatever, is to open registration
on August 2. I'm going to be in Los Angeles doing Rails training, so
it's a bit dependent on hotel connectivity and stuff, and it will
probably be in the evening, Pacific time.

I'm tinkering with the form.... We're using an outside registration
service for the first time, so I have to make sure I get it right, and
it's actually pretty complicated (I think). We got our credit card
merchant account, so we're good to go on that score.

We'll announce it on mailing lists and on the Ruby Central site
(http://www.rubycentral.org), and wherever else we can think of


David

--
http://www.rubypowerandlight.com => Ruby/Rails training & consultancy
http://www.manning.com/black => RUBY FOR RAILS (reviewed on
Slashdot, 7/12/2006!)
http://dablog.rubypal.com => D[avid ]A[. ]B[lack's][ Web]log
(e-mail address removed) => me

 

[Tom Werner]

My current plan, barring unforeseen whatever, is to open registration
on August 2. I'm going to be in Los Angeles doing Rails training, so
it's a bit dependent on hotel connectivity and stuff, and it will
probably be in the evening, Pacific time.

Given the small number of spots for the conference and the large number
of people who want to fill those spots, I wonder if a two stage
registration would be more egalitarian. Stage one would involve the
collection of details for anyone wanting to register (open for perhaps
two or three days). From this (probably staggering) pool of potential
registrants, the chosen few would be picked at random and their payments
would be collected in the second stage.

While this approach would be a bit more work than just opening the
registration floodgate and watching with horror (or delight?) the
ensuing stampede, it would at least mean a fair chance for those who
find themselves on the toilet when you press the magic button.

On one hand, perhaps the hardcore, with their polling scripts and high
blood pressure, deserve to be rewarded with admission, but on the other
hand, there are a lot of us that are nearly, but not quite, as hardcore
who want to attend just as badly.

Regards,

Tom

--
Tom Werner
Helmets to Hardhats
Software Developer
(e-mail address removed)
www.helmetstohardhats.org

 

[N Okia]

I'd like to second Tom's suggestion. Given the supply vs. demand on
this one, I would like to see a lottery. I live only a few blocks from
the Convention location this year, and will be most disheartened if I
cannot get in. However, I'd be much happier if I have an equal shot
with the 'campers'

 

[Jim Freeze]

---------- Forwarded message ----------
From: Tom Werner <[email protected]>
On one hand, perhaps the hardcore, with their polling scripts and high
blood pressure, deserve to be rewarded with admission, but on the other
hand, there are a lot of us that are nearly, but not quite, as hardcore
who want to attend just as badly.

Now there is a great idea for the next Ruby quiz.
A script that monitors email for Rubyconf opening and
then auto registers you for the conference.

JEGII, consider this my submission.

 

[James Edward Gray II]

---------- Forwarded message ----------
From: Tom Werner <[email protected]>
On one hand, perhaps the hardcore, with their polling scripts and high
blood pressure, deserve to be rewarded with admission, but on the
other
hand, there are a lot of us that are nearly, but not quite, as
hardcore
who want to attend just as badly.

Now there is a great idea for the next Ruby quiz.
A script that monitors email for Rubyconf opening and
then auto registers you for the conference.

JEGII, consider this my submission.

I would rather not lead the Denial of Service attach on Ruby
Central.

If you guys really can write a script that properly submits before
you have seen the form though, you are a lot cooler than I am!

James Edward Gray II

 

[Eric Armstrong]

The organizers may already know about this, but
I'll pass it along just in case...

I heard once that when you sign up for space at
a hotel, you can adjust the size of the room up
or down depending on the number of registrations
you get.

They have all those folding partitions they use
to make rooms larger or smaller, you wind up
getting charged for the space you actually use.

There is probably some lead time to take in
account (a week? two?). But it's one to go to
prevent having to "plan small" to be safe...

 

[Tom Werner]

Given the small number of spots for the conference and the large
number of people who want to fill those spots, I wonder if a two stage
registration would be more egalitarian. Stage one would involve the
collection of details for anyone wanting to register (open for perhaps
two or three days). From this (probably staggering) pool of potential
registrants, the chosen few would be picked at random and their
payments would be collected in the second stage.

While this approach would be a bit more work than just opening the
registration floodgate and watching with horror (or delight?) the
ensuing stampede, it would at least mean a fair chance for those who
find themselves on the toilet when you press the magic button.

On one hand, perhaps the hardcore, with their polling scripts and high
blood pressure, deserve to be rewarded with admission, but on the
other hand, there are a lot of us that are nearly, but not quite, as
hardcore who want to attend just as badly.

Regards,

Tom

Another interesting thing this would accomplish is to determine with
absolute certainly how many people actually *are* interested in
attending the conference (providing better audience knowledge to the
decision makers when it comes time to plan for next year's RubyConf).

Tom

--
Tom Werner
Helmets to Hardhats
Software Developer
(e-mail address removed)
www.helmetstohardhats.org

 

[Gregory Brown]

Another interesting thing this would accomplish is to determine with
absolute certainly how many people actually *are* interested in
attending the conference (providing better audience knowledge to the
decision makers when it comes time to plan for next year's RubyConf).

Slap a page on the RubyGarden wiki, I imagine if people want to
express interest they will, though I don't know this can change the
amount of seats available.

 

[M. Edward (Ed) Borasky]

---------- Forwarded message ----------
From: Tom Werner <[email protected]>
On one hand, perhaps the hardcore, with their polling scripts and high
blood pressure, deserve to be rewarded with admission, but on the other
hand, there are a lot of us that are nearly, but not quite, as hardcore
who want to attend just as badly.

Now there is a great idea for the next Ruby quiz.
A script that monitors email for Rubyconf opening and
then auto registers you for the conference.

JEGII, consider this my submission.

Ah, but for performance, shouldn't you write the script in C?