# RubyConf 2006 registration pre-info

**URL:** <https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351>\
**Category:** Ruby\
**Created:** [July 28, 2006, 3:41pm UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351 "2006-07-28T15:41:09Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 28, 2006, 3:41pm UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/1 "2006-07-28T15:41:09Z")

</div>

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 A. 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](http://www.rubycentral.org)), and wherever else we can think of 🙂

David

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 28, 2006, 10:09pm UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/2 "2006-07-28T22:09:41Z")

</div>

removed\_email\_address@domain.invalid wrote:

> My current plan, barring unforeseen whatever, is to open registration  
> on August 2. I’m going to be in Los A. 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

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 28, 2006, 11:00pm UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/3 "2006-07-28T23:00:04Z")

</div>

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’ 🙂

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 28, 2006, 11:46pm UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/4 "2006-07-28T23:46:21Z")

</div>

---------- Forwarded message ----------  
From: Tom W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
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. 🙂

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 29, 2006, 12:33am UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/5 "2006-07-29T00:33:16Z")

</div>

On Jul 28, 2006, at 4:44 PM, Jim F. wrote:

> 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 G. II

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 29, 2006, 1:19am UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/6 "2006-07-29T01:19:22Z")

</div>

Tom W. wrote:

> registration would be more egalitarian. Stage one would involve the  
> 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

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 29, 2006, 12:56am UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/7 "2006-07-29T00:56:45Z")

</div>

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…

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 29, 2006, 4:42am UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/8 "2006-07-29T04:42:38Z")

</div>

Jim F. wrote:

> JEGII, consider this my submission. 🙂

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

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [July 29, 2006, 3:48am UTC](https://www.ruby-forum.com/t/rubyconf-2006-registration-pre-info/100351/9 "2006-07-29T03:48:11Z")

</div>

On 7/28/06, Tom W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> 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.
