---
name: event management
status: proposal
---

# Problem statement

Not the ad-space - but the event management, sign-up space.

# Operative user requirements

- Overview of events and their repetition
- ID-management
  - Only the needed data
  - ID = email, and so we can let you know if we cancel
  - Name - To give the instructor a ledger to tick off
  - Comment field
  - Profile picture
  - People who are signed up, can see others who are signed up for the same event
  - Members are automatically set up
    - Login via OM-key-chip?
- Communication system
  - COM = email
  - Receipt for sign-up
  - event materials
  - Reminders...
- Open standards
  - Vcard or similiardstandard
  - JSON or XML
  - FLOSS (MIT or lighter)
- SSO
  - Authentik
  - Oauth
- Security
  - Own hosting
  - 3-2-1 backup
  - Uptime: 99.9 (but we try for more)
  - HA
  - Loki+Grafana Alloy+Grafana alerts
  - Supply-chain / dependencies
  - GIT
- Separation of concerns
  - Sign-up and things directly related to each event
  - event catalogue/program
  - Advert
    - SoMe
    - Newsletter
    - MeshCore
  - Who graduated
- Admin stuff
  - Wait lists
  - Max number of participants
- SSoT: Where is the event described
  - Here or on Facebook?
- Adding new events
  - Templates
  - Repeatable
  - Idea: All can add new events
  - Depreciated for now: Is English an option?
- How are people updated on what happens
  - RSS
  - Dedicated newsletter
  - Bot on Matrix
- Shareable - so no login unless required. Short links/SoMe/e-mail/chat...
- Application in Danish
- Responsive
- GDPR compliant
- High trust (readable links), HTTPS
- Do one (a few) things well
- Modular - so we can drop or add things
- Very clear for the user to understand if they did the right thing
- Easy for the user - and for the admin and the AI. Proper headers so that when you post about in on SoMe it picks up the rights graphics
- REST-API

# PoA

- Marcus - Talk with Kjeld about moving over to GIT
- PR FTW