Minimal Event and Crew specifications

[niccofyren]

This outlines the minimal parts we need in place to unblock other models that rely on the Event concept. We expect lots of additional functionality outside of this before Wannabe5 core is finished, but main goal now is to block other parts getting developed.

Event

Example; The Gathering 2025, The Gathering 2024, TG Online, ...
Existing model: https://github.com/gathering/wannabe5-backend/blob/main/microservices/crew/app/Models/Event.php

Fields

• Name
• Slug (we generally use this in frontend urls)
• Location (string)
• Start and end date
• state (enum: hidden, closed, open)*

Connections

• Multiple Crews

• Yes, this is different than in existing backend. I suspect we want to make sure these states can't overlap in confusing ways. Ie. not allow an event to be both hidden and open. But feel free to experiment

Crew

Example; Ledergruppen, Event, Event:Innhold, Event:Innhold:Achievements
Existing model: https://github.com/gathering/wannabe5-backend/blob/main/microservices/crew/app/Models/Crew.php

Fields

• short description (plain string for now)
• long description (plain string for now)
• state (enum: hidden, closed, open)*

Connections

• One Event - Crews are unique per year/event
• One parent crew - Crews can be nested under each other, see example above
• Multiple Users - Each crew has multiple users (role and team related details can be skipped for now)

• See event note

Crew teams and roles

Can be skipped in initial version