--- urn: "urn:penemure:12b16b36-bed6-4adf-88d5-0bd3c0219328" backend: "pub" ancestors: - 📁 Penemure created: 2025-01-24 10:36:25.283390+00:00 updated: 2025-01-24 10:36:25.283398+00:00 tags: --- # 📓 Review of Initial Goals ## Projects Aspect | Status | Notes --- | --- | --- title (v0) | ✅ | description (v0) | ✅ | roles (v0) | No | Only makes sense in a server-based environment, where the participant does not have access to the files start/end dates (use this when showing date pickers) (v0) | ❌ | key resources (docs/pdfs/logos/etc.) (v1) | ❌ | attachments are there but no good way to query/link them in as nice chunky blocks Child projects with own sharing (v1) | ✅ | accomplished via git overlay engine filter out blocked. (v0) | ❌ | Groups of Tasks | ❌ | what did she mean by this? The world will never know ### Views Aspect | Status | Notes --- | --- | --- List | ✅ | Timeline | ✅ | Board| ✅ | Calendar | ❌ | Workflows | ❌ | Dashboards (low) | ✅ | Maybe?? We've got charting abilities, that's sufficient right? ## Tasks Aspect | Status | Notes --- | --- | --- title (v0)| ✅ | description (v0)| ✅ | start/end (exact or relative to project, e.g. M1/Q1) (v1) | ❌ | no date picker yet. Attachments/FILES (v0) | ❌ | needs Drag and Drop UX tags (v0)| ✅ | assignees (v0) | ❌ | No assignee picker yet children (subtasks) (v0)| ✅ | blocking/blocked-by (v0) | ❌ | No issue picker yet projects: multiple selection (v0)| ✅ | in project: | ? | Group of Tasks - ibid, does it mean like, lists within a project? can this be modelled as a task? ## Repeating Tasks Aspect | Status | Notes --- | --- | --- daily/weekly/etc.| ❌ | decide behaviour on completion/missing (does it just disappear? is it tracked?)| ❌ | from a 'template'?| ❌ | given a 'parent' task, does it generate subsequent ones? Are they real (existing on disk) or synthetic.| ❌ | if we didn't want a 'full' version of properly calendered repeating events we could go for the 'cheap' version of schedule N future copies of this, without the ability to edit one/all future events| ❌ | That's calendaring. That's just fucking calendaring, you're insane. stop it.| ❌ | ## Time Tracking (v1) Aspect | Status | Notes --- | --- | --- Easily enter a task and start it| ✅ | Back date time | Not fully implemented | associate to a specific task| ✅ | one task can be made up of multiple time-management segments, maybe they're also conceptually 'tasks', just a 'quick subtask' ## Server Aspect | Status | Notes --- | --- | --- Server implementation | ✅ | Auth | TODO | ## People Aspect | Status | Notes --- | --- | --- Allow assigning people without them existing in the system | Supported: Requires picker | just @ them. If a @{user} exists, use that for avatar/etc. ## Teams Aspect | Status | Notes --- | --- | --- Create arbitrary sub-groups of teams | ✅ | natively supported, and different viewers can have different views via overlays. ## Workflows (v2) Aspect | Status | Notes --- | --- | --- Move tasks around| ❌ | modify them| ❌ | Re-assign, etc.| ❌ | ## Forms (v2) Aspect | Status | Notes --- | --- | --- Implement Forms | ❌ | Basically simplified issue creation with mandatory fields. Really only needed on the 'hosting' server, less important locally. ## Import Aspect | Status | Notes --- | --- | --- import from notion | ❌ | import from calendar | ❌ | (generate an associated task that follows a calendar event around / can automatically have reminders.)