Kocoder/obsidian
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2026-02-27 10:43:35

Browse Source
This commit is contained in:
Konstantin Hintermayer
2026-02-27 10:43:36 +01:00
parent cf4bb46286
commit dcfaa481bd
13 changed files with 1405 additions and 139 deletions
Download Patch File Download Diff File Expand all files Collapse all files

70
Test/EventKit/08 - Open Questions.md
View File

@@ -13,27 +13,27 @@ Remaining decisions and questions that need answers before or during implementat
## Business & Scope
| # | Question | Options / Notes |
| --- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| 1 | **Primary equipment types** — which sectors will be supported first? | Audio, lighting, video, staging, rigging, power, furniture, décor — prioritise for MVP |
| 2 | ~~**Target company size** — small (1-5 people) or larger (20+)?~~ | ✅ **Answered**: Small to medium companies wanting to share resources. Both scales should be possible |
| 3 | **Pricing model** — how will EventKit itself be offered? | Open source, freemium, paid self-hosted licence, or SaaS alongside self-hosted? |
| 4 | **MVP scope** — which module to build first? | Inventory + Scanning → Planning → CRM → Federation is a natural order |
| 5 | ~~**Data migration** — what systems are companies migrating from?~~ | ✅ **Answered**: Nice-to-have future feature. Import tooling not a priority for MVP |
| # | Question | Options / Notes |
| --- | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| 1 | ~~**Primary equipment types** — which sectors first?~~ | ✅ **Answered**: Audio, Lighting, Rigging, Power distribution for MVP |
| 2 | ~~**Target company size** — small (1-5 people) or larger (20+)?~~ | ✅ **Answered**: Small to medium companies wanting to share resources. Both scales should be possible |
| 3 | ~~**Pricing model** — how will EventKit itself be offered?~~ | ✅ **Answered**: Open core — free self-hosted, paid SaaS with premium features |
| 4 | ~~**MVP scope** — which module to build first?~~ | ✅ **Answered**: Inventory + Scanning → Planning → CRM → Federation |
| 5 | ~~**Data migration** — what systems are companies migrating from?~~ | ✅ **Answered**: Nice-to-have future feature. Import tooling not a priority for MVP |
---
## Technical
| # | Question | Options / Notes |
| --- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| 6 | ~~**Tech stack** — backend language and framework?~~ | ✅ **Decided: Go** with ConnectRPC |
| 7 | ~~**Frontend framework**~~ | ✅ **Decided: React** with @tanstack/router + @tanstack/query. Mobile: React Native / Expo (planned, not priority) |
| 8 | ~~**Database**~~ | ✅ **Decided: PostgreSQL 15+** |
| 9 | **Search engine** | Built-in DB search, or dedicated (Meilisearch, Typesense) for large catalogues? |
| 10 | **File storage** | Local filesystem, S3-compatible, or both? |
| 11 | **Real-time updates** | gRPC server-streaming (via ConnectRPC) is the natural choice. SSE fallback for browsers? |
| 12 | **Background jobs** | Go goroutines + internal queue, or external (Redis, NATS)? |
| # | Question | Options / Notes |
| --- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| 6 | ~~**Tech stack** — backend language and framework?~~ | ✅ **Decided: Go** with ConnectRPC |
| 7 | ~~**Frontend framework**~~ | ✅ **Decided: React** with @tanstack/router + @tanstack/query + shadcn/ui. Mobile: React Native / Expo (planned, not priority) |
| 8 | ~~**Database**~~ | ✅ **Decided: PostgreSQL 15+** |
| 9 | ~~**Search engine**~~ | ✅ **Answered**: PostgreSQL full-text search first, dedicated engine (Meilisearch) later if needed |
| 10 | ~~**File storage**~~ | ✅ **Answered**: Both — local filesystem + S3-compatible, configurable per deployment |
| 11 | ~~**Real-time updates**~~ | ✅ **Answered**: Not from the start. Future nice-to-have via gRPC server-streaming |
| 12 | ~~**Background jobs**~~ | ✅ **Answered**: External broker (NATS or Redis) — suited for Kubernetes deployment |
---
@@ -45,19 +45,19 @@ Remaining decisions and questions that need answers before or during implementat
| 14 | ~~**Protocol format**~~ | ✅ **Decided: gRPC via ConnectRPC** with Protobuf service definitions |
| 15 | ~~**Pricing in federation** — should sub-hire rates be shared automatically?~~ | ✅ **Answered: Prices negotiated per-transaction** — out-of-band negotiation, system tracks equipment movement |
| 16 | ~~**Asset ownership transfer** — can an asset be permanently sold to another instance?~~ | ✅ **Answered: Yes** — permanent ownership transfer is supported |
| 17 | **Federation versioning** — how to handle protocol upgrades? | Protobuf's built-in backward compatibility helps here |
| 18 | **Dispute resolution** — what happens if companies disagree about asset condition? | Photo evidence at dispatch/return, timestamped condition logs |
| 17 | ~~**Federation versioning** — how to handle protocol upgrades?~~ | ✅ **Answered**: Protobuf backward compat, document breaking changes, no formal version negotiation |
| 18 | ~~**Dispute resolution** — what happens if companies disagree about asset condition?~~ | ✅ **Answered**: Timestamped condition logs + out-of-band dispute handling |
---
## Scanning & Hardware
| # | Question | Options / Notes |
| --- | ------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| 19 | **Primary scanning device** — phone cameras or dedicated scanners? | Phones (lower cost) vs. Bluetooth scanners (faster) vs. both |
| 20 | **Label printer** — should EventKit support direct printing? | Or generate PDFs and let users print on any printer? |
| 21 | ~~**Existing barcodes** — do companies already have asset labels?~~ | ✅ **Answered: Yes, support legacy barcode import/mapping** if possible |
| 22 | ~~**Offline requirements** — how often will users be offline?~~ | ✅ **Answered: Nice-to-have**, not a hard requirement |
| # | Question | Options / Notes |
| --- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| 19 | ~~**Primary scanning device** — phone cameras or dedicated scanners?~~ | ✅ **Answered**: Both — phone camera default, Bluetooth scanner as power-user option |
| 20 | ~~**Label printer** — should EventKit support direct printing?~~ | ✅ **Answered**: PDF default, direct printing optional |
| 21 | ~~**Existing barcodes** — do companies already have asset labels?~~ | ✅ **Answered: Yes, support legacy barcode import/mapping** if possible |
| 22 | ~~**Offline requirements** — how often will users be offline?~~ | ✅ **Answered: Nice-to-have**, not a hard requirement |
---
@@ -67,8 +67,8 @@ Remaining decisions and questions that need answers before or during implementat
| --- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 23 | ~~**Invoicing depth** — full invoicing or integration with existing accounting?~~ | ✅ **Answered: Integrated accounting features are the priority.** Xero/QuickBooks integration is optional/secondary. Invoices, payments, and purchases all in-app |
| 24 | ~~**Accounting integrations** — which platforms?~~ | ✅ **Answered: Xero and QuickBooks** — optional, not priority. Integrated features come first |
| 25 | **Email integration** — built-in email or link to external? | IMAP/SMTP integration vs. Gmail/Outlook API vs. just logging |
| 26 | **Marketing features** — email campaigns needed? | Or leave marketing to dedicated tools (Mailchimp, etc.)? |
| 25 | ~~**Email integration** — built-in email or link to external?~~ | ✅ **Answered**: Full IMAP/SMTP with sub-addressing for routing emails to projects/clients |
| 26 | ~~**Marketing features** — email campaigns needed?~~ | ✅ **Answered**: Not for now — leave to dedicated tools |
---
@@ -77,22 +77,15 @@ Remaining decisions and questions that need answers before or during implementat
| # | Question | Options / Notes |
| --- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| 27 | ~~**Crew management depth** — basic assignment or full scheduling?~~ | ✅ **Answered**: Crew members login and confirm availability. Basic scheduling with crew portal |
| 28 | **Transport planning** — basic or advanced? | Basic: assign vehicles. Advanced: route optimisation, weight distribution |
| 29 | **Venue database** — shared across instances? | Could be a federated feature — shared venue specs across the network |
| 30 | **Calendar integration** — which platforms? | Google Calendar, Outlook/Exchange, CalDAV — for crew and event sync |
| 28 | ~~**Transport planning** — basic or advanced?~~ | ✅ **Answered**: Start basic → intermediate (weight/volume) → advanced (route optimisation) |
| 29 | ~~**Venue database** — shared across instances?~~ | ✅ **Answered**: Start local, federate later |
| 30 | ~~**Calendar integration** — which platforms?~~ | ✅ **Answered**: CalDAV + iCal export for MVP. Google Calendar + Outlook/Exchange later |
---
## Priority Matrix
Suggested priority for answering these questions:
| Priority | Questions | Reason |
| -------------------------------------- | --------------------------- | ------------------------------------------------- |
| ✅ **Answered** | 2, 5-8, 13-16, 21-24, 27 | See strikethrough items above |
| 🔴 **Must answer before starting** | 1, 4 | Scope (which equipment sectors first, MVP order) |
| 🟡 **Answer during early development** | 3, 9-11, 19 | Affects architecture but can be deferred slightly |
| 🟢 **Answer before beta** | 12, 17-18, 20, 25-26, 28-30 | Important but not blocking initial development |
All 30 questions have been answered. ✅
---
@@ -106,4 +99,5 @@ Suggested priority for answering these questions:
- [[05 - Barcode and QR Scanning]] — Scanning and hardware
- [[06 - Module Integration]] — Cross-module workflows
- [[07 - Technical Requirements]] — Technical decisions made and remaining
- [[09 - Discovery Questions]] — Original discovery questionnaire with answers
- [[00-DiscoveryQuestions]] — Round 1 answers
- [[01-DiscoveryQuestions]] — Round 2 answers