divviup / divviup/divviup-api

What tools should we have for management of large number of tasks?

Open
#380 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

TBD/Design/Discussion phase
Dominant language
Rust
Stars
10
Forks
5
Avg merge
2h 41m
Merged PRs (30d)
66

Description

Since each task represents a single measurement to be taken, it's plausible that large applications may have hundreds or even thousands of tasks. A simple list of tasks would not be sufficient for organizing and navigating through them.

Even for smaller numbers of tasks, tasks would benefit from a logical grouping (e.g. these tasks are for my application Foo, and those are for application Bar).

Some possible strategies off the top of my head:

  • Task groups. Alternative names: namespace, project.
  • Task tags.

Bonus: it should be designed to make way for a future more sophisticated permissions model (e.g. Alice is a developer for Foo, should only be able to manage Foo tasks).

Without this, we run the risk of people organizing by creating multiple Accounts, which may complicate billing.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by surveying how tasks and accounts are represented and managed, then clarify whether grouping, tags, permissions, or another approach is wanted; done should include an agreed design and its implementation criteria.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.