Skip to content
This repository has been archived by the owner on Mar 8, 2018. It is now read-only.

[FR] Invitation system UI #14

Open
webknjaz opened this issue Jul 9, 2013 · 5 comments
Open

[FR] Invitation system UI #14

webknjaz opened this issue Jul 9, 2013 · 5 comments

Comments

@webknjaz
Copy link
Member

webknjaz commented Jul 9, 2013

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

@ghost ghost assigned olostan Jul 9, 2013
@olostan
Copy link
Member

olostan commented Oct 23, 2013

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
Copy link
Member Author

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
Copy link
Member

olostan commented Oct 24, 2013

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
Copy link
Member Author

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
Copy link
Member Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants