geeksoflondon / hamster Goto Github PK

Diet is in the schema.rb but is not in the model or have any validation.

Quoting @mseckington

"we should be using the expect syntax in rspec, rather than should, but we can change that all in one go later."

Attendees do not have a kind but tickets do.

Requirements:

• Default json routes
• Disable assets
• Ignore all unnecessary files

Model is already in code

Just an idea. Allow for any other app to use hamster as its authentication endpoint would be nice.

We're just going to put it all in 1 app and load balance that.

In order to gain access to the onsite registration system, a staff member can scan in with their special wristband.

• only special wristbands can scan into the system

Following on discussion with @mseckington we need to define the language we use for defining attendee state.

Currently these are:

- *attending*  attendee is either confirmed or still unconfirmed
- *attended* attendee has arrived at the event
- *on-site* attendee is in the venue
- *off-site* attendee is out of the venue
- *confirmed* attendee has confirmed they are attending via retain
- *unconfirmed* attendee has not confirmed they are attending via retain
- *cancelled* attendee has cancelled their ticket via retain

We need some proposals for making this language clearer.

We should standardize the data for import.

So we have some existing apps, right? Could you tell me where the existing data for those is, and maybe export it and put it in dropbox or something?

Have a working set of seeds so that we can build features.

I suggest we use ActiveResource for this for the basics.

Probably should be a seperate project.

I suggest we go for hamster-rb

ActiveResource pagination gem expects has_many relationships to exist as nested resources

(fname, sname, twitter)

We need to store events in hamster.