Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactoring: introduce Slot(s) #276

Open
cbellone opened this issue Apr 12, 2017 · 0 comments
Open

Refactoring: introduce Slot(s) #276

cbellone opened this issue Apr 12, 2017 · 0 comments
Assignees
Milestone

Comments

@cbellone
Copy link
Member

cbellone commented Apr 12, 2017

We should decouple the ticket from the seat.
Introducing the concept of "slot" (a "seat" in a fixed-seats event) would give us more flexibility with respect to:

  • cancelled / expired reservations: we can save the expired or cancelled reservation (including tickets) for reuse
  • we can create tickets dinamically as people generate them.
  • we can limit the validity of a ticket only to a part of the conference (e.g. single-day access) by linking the ticket to more slots
  • etc.

The concept of slot would be general and not strictly related to tickets. It could come in handy also for #111

@cbellone cbellone added this to the 1.11 milestone Apr 12, 2017
@syjer syjer modified the milestones: 2.0, 1.11 May 4, 2017
@cbellone cbellone modified the milestones: 2.0, 2.0-M3 Sep 26, 2019
@cbellone cbellone modified the milestones: 2.0-M3, 2.0-M4 Sep 2, 2020
@cbellone cbellone modified the milestones: 2.0-M4, 2.0 Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants