This post originated from an RSS feed registered with Ruby Buzz
by James Britt.
Original Post: RubyConf 2005 Registration is Open
Feed Title: James Britt: Ruby Development
Feed URL: http://feeds.feedburner.com/JamesBritt-Home
Feed Description: James Britt: Playing with better toys
Word of caution: Registration requires that you've already preregistered. Which I had done; if you haven't, it is apparently still a requirement, even though actual registration is open. There is a link to a registration page where you enter your user name and password, and submit a form. On the following pages is where the actual registration and payment takes place, unless there is a problem, as was my case.
You get a choice of paying by PayPal or check. The details for paying by check are on this registration page; make a note of them.
If you have a PayPal account you can use that, assuming you know your log-in info. I created a PayPal account some time ago but could not recall the details, so I went for the "pay by credit card by way of PayPal" option. This was a mistake.
After entering all my info, and submitting the payment form, I was told that my credit card account was already in use by an existing PayPal account, and that I would have to use that account to use that credit card. Hooray for the Web!
Well, hell, I had no idea what E-mail address to use or what my the password might be, and decided I would just pay by check. Except now I was past the page with the pay-by-check details.
I tried to retrace my steps, but the site is set up that once you submit that initial registration form you are considered registered, even if you've not paid. And there does not seem to be any way to get to that check payment info or retry the PayPal approach.
So don't screw up. I had to E-mail David Alan Black for the payment address.
(I've since recovered my PayPal account and would prefer to just use that, but cannot find a way to do this, so by check it must be.)
BTW, you can see the conference agenda here. There are a number of topics about or involving Rails, which offers a bit of irony. It seems that the conference site (a Rails application) had suffered crashes, and some presentation proposals were lost. Those whose submissions got, um, derailed did not find out about it until the anouncement of the actual agenda.
Previous Topic
