search

GDG-Ukraine / gdgregform

[DEPRECATED] Contacts DB and registration forms admin UI
http://reg.gdg.org.ua/
2 stars 1 forks source link

[FR] Invitation system UI #14

Open webknjaz opened 11 years ago

webknjaz commented 11 years ago

Implement $sbj. DB structure for it already exists. Table is gdg_invites and it contains following values: (code = 32 chars, email, event_id, used)

olostan commented 11 years ago

I assume we do not need "email" field and "used" should be reference to participant when it was used or null if not.

I do not see any reason to use "email" field - invites could be printed and given in some prior events/meetup/hackathons as prizes, so we do not know email who will use this invite.

webknjaz commented 11 years ago

Now it doesn't work this way.

What if I want to restrict invite to some specific email address? Also probably it's reasonable to save invite creator and notify him once invite is used.

olostan commented 11 years ago

So email is email restriction? ok. email restriction and notifications could be nice features to have... may be as separate [FR] but for used - its better to change the way I've described.

webknjaz commented 11 years ago

So email is email restriction? ok.

Now it's not. but it was designed to be. So we can decide to re-design table structure at this stage.

may be as separate [FR]

go on

but for used - its better to change the way I've described.

I agree regarding used. But it is BOOL or so as for now.

webknjaz commented 11 years ago

UPD: probably we need to have additional notes/metainformation on each invite.