Registration

From MelbLCAWiki

Jump to: navigation, search

Contents

Introduction

All issues to do with registration

How much should student registration be? (and hobbyist , professional)

should we be limiting numbers to registration types? (only 100 hobbyists , for example)

The Registration Software

There have been several complete different implementations.

Because doing a rewrite is always good!? err... perhaps not.

In Dunedin we're having a BoF to help assemble all the versions and then build up a team for getting a "One Ring (err.. version) to rule them all" that can be hacked on going into the future. Obviously, we want to talk with the 07 people about this too.

StewartSmith is going to be at the BoF. discussions have been on the lca-ghosts list.

In theory Sydney will be using this newly assembled version? - Sydney wrote their own. It uses Python / Pylons.

Rough notes for functionality

Call for papers

  • submission
  • evaluation
  • voting
  • speaker location - critical information for budgetting.

Important to capture full contact details for potential speakers. Also - some indication of judging criteria would be helpful. this means we need to determine it up in advance.

Registration system

  • call for papers submissions triggers an account - whether accepted or not it should be possible to easily register for the conference.
  • payment for registration, and accomodation, and extra events.

Badge Data / Accounting Data / Profile - info

  • Firstname, Secondname, Description (eg business, occupation, project etc)
  • Address details (for accounting and contact purposes)
  • street address / postal address
  • suburb/city, state/province, postcodes, country codes
  • phone numbers,
  • email addresses (include space for an alternate address, and a user toggle for preferred address)

Travel Plans? - somewhere to store this info? (possibly useful for future planning)

Dietary / Mobility considerations.

Admin Functionality

Track Registrations - how many, from where - locals, interstate, internationals. Track Payments - needs to integrate / export into some form of accounting system.

Past LCA Registration Fees

Past LCA Registration Fees
Professional Hobbyist Concession Dinner Tickets
2008 $750 / $600 $350 / $280 $150  ?
2007 $690 / $517.50 $300 / $225 $99 $60
2006 $690 / $517.50 $300 / $225 $100 $60
2005 $690 / $460 $300 / $200 $100 $60
2004 $600 $275 $99 $60
2003 $550 $250 $99 $50
2002 $550 $250 $99 $50

For Comparison:

Germany's Linux-Kongress 2006 Fees

 Normal Students
4 days 560 EUR185 EUR
3 days 420 EUR150 EUR
2 days 320 EUR105 EUR
1 day 180 EUR60 EUR
Social 24 EUR24 EUR

All prices include 16% VAT. Members of GUUG and NLUUG will get a reduction of 25% on the prices given above.

Canada's Linux Symposium

 Standard Students
By April 1 350.00 CAD 200.00 CAD.
By June 1 500.00 CAD 250.00 CAD.
After June 1 750.00 CAD 275.00 CAD.

Student Registrations

Must show ID on the day to register - and email a scan or post or fax a photocopy at time of payment.

As the conf is in January, most often before uni registration we should allow id's from previous year.

We should also define what qualifies, ie. undergraduage, post-grad etc.

Miniconf only registrations

Do we wish to allow?

This is probably part of a more general question - whether to allow "day registrations". A difference with the MiniConf days is that there (probably?) won't be keynotes, so the size of the largest theatre is less relevant as a limit. On the other hand, Mon/Tue-only attendees who can't get into the one MiniConf that they are interested in may be more annoyed than whole-conf attendees that can't get into a particular talk. --Jiri 02:27, 3 Apr 2006 (EST)

Sign-in issues

Have IRC client on Freenode in Channel with nick highlight on "rego" or "desk" from Sunday morning.

Talk to FreeNode ~10-8 weeks out for lca.irc.freenode.org server (either Christel or Rob will do it for us).


When people show up on Sunday-Wednesday to sign in they get:

  • Badge - Personal, pre-printed
  • Schwag - By registration type
  • T-Shirt - By Size

We need to require them to show some proof:

  • Photo ID OR printed copy of registration conformation
  • Student ID of previous year for student registrations

Queues should be set up as:

  • A-K
  • L-Z
  • Speakers
  • Guests / Media --

Partner registrations should be attached to the badge of the delegate

Personal tools