@@ -0,0 +1,69 @@
6+grant_type = ["Proposal"]
7+grant_category = ["App Dev"]
11+description = "Goals 2"
13+assignee = ["~niblyx-malnus, ~sidlup-havwen"]
15+champion = ["~datder-sonnet"]
24+- Full association of a pool with a group.
25+ - The pool is public or private in correspondence with the group.
26+ - The pool has the same set of banned/allowed ships as the group.
27+ - All group admins are automatically admins on the pool.
28+ - Members who leave or are kicked from the group are automatically removed from the pool.
29+ - Members who join the group are automatically added to the pool.
30+- Each pool and goal will have an associated note. A note is a piece of markdown used to flesh out the pool or goal in greater detail.
31+- Each pool and goal will have an associated comment section where pool members can comment on the specific details of the goal.
32+- Both notes and comments will be able to link to existing nodes in Groups which will render appropriately. This includes chats, notes, channels, comments, entire groups, and applications.
33+- Both notes and comments will be able to link to existing pools and goals which will render similarly to Groups nodes.
34+- Significant events trigger notifications to be sent via %hark. These include:
35+ - Being assigned to be chief of a goal.
36+ - Being assigned to be in the spawn set of a goal.
37+ - New goals spawned under goals you own.
38+ - Non-actionable goals with no subgoals being left childless for an extended period of time.
39+ - Other events as they emerge and are deemed appropriate.
41+## Sorting/Filtering and Tags/Fields
44+ - Each goal within a pool can be tagged.
45+ - Everyone can maintain private tags associated with a goal which only they can view.
46+ - Harvested goals can be sorted by tags.
47+ - Tags can be viewed so that all goals associated with them can be seen and explored.
48+- Sorting/Context-based Ordering
49+ - Goals can be sorted by the date of their deadline or kickoff.
50+ - Goals can be re-ordered in the context of their subgoals with a simple dragging mechanism.
54+- Incorporate a calendar view which draws from a separate agent allowing for the possibility that it could grow into a full blown calendar application.
55+ - A frontend calendar view can scry this agent for events within a particular range (initially corresponding only to goals).
56+ - If a goal has both a kickoff and a deadline, it will display in the calendar with this datetime range showing. If either only the kickoff or deadline exists, the kickoff or deadline of that goal will display as an instantaneous event.
57+ - Goals which span many days will be displayed differently than goals which or on the order of a few hours.
61+- Shortcuts and quick actions using ctrl
62+- Improved mobile experience
63+- Navigating the tree (zooming/isolation) with a breadcrumb element (clickable links) for navigating back (possibly incorporating notes and comment section)
64+- Incorporate tagging system into a Kanban view
65+- Working poke relays on the frontend