Central calendar for the LIT like a dumpster fellars .
- Rust 64.8%
- Nix 35.2%
| src | ||
| .gitignore | ||
| calenducks.ron | ||
| Cargo.lock | ||
| Cargo.toml | ||
| default.nix | ||
| flake.lock | ||
| flake.nix | ||
| README.typ | ||
| rustfmt.toml | ||
#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