Problem
Events become more useful when people can mark interest, communities can model recurring events, and profile/home surfaces can derive more personal event context. VRDex should capture this direction without forcing it into the first event CRUD slice.
Scope
- define an event interest or RSVP model
- distinguish lightweight interest from official participation or lineup association
- define a recurring-event or event-series model
- support recurring events without duplicating stale data forever
- leave room for event feeds such as events a person follows, attends, or is interested in
- preserve source/provenance where interest data is imported or synced
Non-goals
- full ticketing
- event reminders and notifications in the first slice
- Google Calendar sync/export implementation
- VRChat private presence tracking
- complete social graph implementation
Acceptance criteria
- event interest/RSVP is modeled separately from participant/lineup association
- recurring events have a documented product and data-model direction
- future home/profile event feeds can build from the model
- imported or partner-provided interest data has provenance boundaries
- the direction is clear enough to become implementation work after the core event model lands
Related
Problem
Events become more useful when people can mark interest, communities can model recurring events, and profile/home surfaces can derive more personal event context. VRDex should capture this direction without forcing it into the first event CRUD slice.
Scope
Non-goals
Acceptance criteria
Related