MakerFLOSS/notes/coursemanagement.md

---
name: coursemanagement
kind: web-app
status: planned
---

# 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
docs(hardware): record DDR4-2666 RAM type for mf01/mf02, fix mf00 status Add ram_type (DDR4-2666 non-ECC UDIMM) to mf01 and mf02 frontmatter, and set mf00's placeholder status to staging so the overview index regenerates. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 2026-06-03 19:10:53 +02:00			`---`
feat(rack): populate rack01 and wire gen_rack into make targets Add rack placement frontmatter to mf00–mf04, fix pre-existing schema error in docs/services/coursemanagement.md (missing kind/name fields), extend Makefile docs-index and docs-check targets to also run gen_rack, add test target, generate rack01.md and rack01-elevation.svg. Positions are provisional placeholders to prove the pipeline; correct when mounting. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> 2026-06-24 13:56:09 +02:00			`name: coursemanagement`
			`kind: web-app`
			`status: planned`
docs(hardware): record DDR4-2666 RAM type for mf01/mf02, fix mf00 status Add ram_type (DDR4-2666 non-ECC UDIMM) to mf01 and mf02 frontmatter, and set mf00's placeholder status to staging so the overview index regenerates. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 2026-06-03 19:10:53 +02:00			`---`

			`# 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`