Central calendar for the LIT like a dumpster fellars .
  • Rust 64.8%
  • Nix 35.2%
Find a file
2026-09-30 12:33:23 +02:00
src initial commit 2026-09-30 12:32:01 +02:00
.gitignore add event database to gitignore 2026-09-30 12:33:23 +02:00
calenducks.ron initial commit 2026-09-30 12:32:01 +02:00
Cargo.lock initial commit 2026-09-30 12:32:01 +02:00
Cargo.toml initial commit 2026-09-30 12:32:01 +02:00
default.nix initial commit 2026-09-30 12:32:01 +02:00
flake.lock initial commit 2026-09-30 12:32:01 +02:00
flake.nix initial commit 2026-09-30 12:32:01 +02:00
README.typ initial commit 2026-09-30 12:32:01 +02:00
rustfmt.toml initial commit 2026-09-30 12:32:01 +02:00

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

#import "@preview/cheq:0.4.0": checklist
#show: checklist

= Calenduck
Central calendar for the LIT like a dumpster fellars .  Anyone can create and edit events, with a central server keeping track .  Uses duckdb in the back to keep the events saved and consistent .

== Roadmap
- [ ] Event protocol
  - [ ] Packet definitions
    - [ ] SetEventInfo
    - [ ] DeleteEvent
    - [ ] GetEventInfo
    - [ ] GetEventsForTimeframe
- [ ] Server
  - [ ] Set up duckdb
    - [ ] Decide on tables
      - Table with event uuid, list of subscribers/attendees, start time, end time
      - User table with names and password hashes
  - [ ] Configuration
    - Registration of users allowed
  - [ ] Translate event protocol operations to duckdb operations where appropriate
  - [ ] Ping clients when a change was made in the database
    Should there be hints on what kind of data has changed or should the change outright be forwarded immediately to all clients currently connected ?
- [ ] Client
  - [ ] CLI client
  - [ ] GUI client