Each tracker can have a "Mission" which is a task in a higher level tracker.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7m
- Merged PRs (30d)
- 3
Description
-
Allow a tracker in its settings to have its mission set to an existing Task in another tracker.
-
Within a task of given tracker, allow the user to create a sub-tracker for the accomplishment of that task. Default the URI of it but also allow that to be
Workflow could be hierarchical, with new tracker just created inside each other, or it could be that the sub-tracker is in a completely different part of the solid space, as work is undertaken by different groups in the world, and so a random link must be possible.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the existing tracker settings and task creation flows, then clarify how a tracker links to a task and how a task creates or references a sub-tracker; done means both workflows support hierarchical and external Solid-space links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100