Foundational concept design: multi-node support

Open

#8 opened on Mar 22, 2020 0 comments 0 reactions 1 assignee View on GitHub

@ForNeVeR is already working on this.

Since Mar 22, 2020.

Assessment

This issue has not been assessed yet.

Description

kind:rfc

Praefectus should support working with multiple nodes. There'll be multiple node from the very beginning: there'll be a Taskwarrior node (with import/export capabilities), and a Praefectus user-facing node (so the user may customize/change the tasks imported from Taskwarrior, with the changes eventually being synchronized back to Taskwarrior).

Here're the questions we'll need to solve while designing this stuff:

should task attributes belong to individual nodes and/or to node types and/or to the global namespace?
how the attributes should be merged if multiple nodes have changed the same attribute?
should we provide a pluggable/configurable merge algorithms?

Depends on:

#6 (since we need to decide on the sorts of information we store in Praefectus first)
#7 (since we need to know how the branching/merging will work before applying it to the multi-node practice)

Dominant language: F#
Stars: 15
Forks: 0
PR merge metrics: No merged PRs in 30d

Getting set up

No Dockerfile or Docker Compose file
No pull request template
Read the contributing guide

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.

Foundational concept design: multi-node support

Is something wrong?

Assessment

Description

Getting set up

First steps

More from ForNeVeR/praefectus

Is something wrong?

Is something wrong?

Is something wrong?

Is something wrong?

Is something wrong?

Get new issues in your inbox