Minimum Viable Product - Githubissues

This issue is a milestone. It groups other issues and gives a bit of motivation for the grouping and prioritizing of them. It is expected that no work will be done in scope of the issue itself; all the work will be done in the issues it depends on.

I didn't wrote anything on this kind of issues in the process document since I expect to use them only on the start of the project, for few first releases, and they aren't important part of the RFC framework.

I want Praefectus to first interop with, and then – eventualy – surpass, the Taskwarrior in my daily routine. Taskwarrior will be the first integration Praefectus gets, and the main/flagship one (for a while, at least).

So, this release will be mostly dedicated to providing the basic infrastructure/fundamentals, and then clean interoperation mode with Taskwarrior.

Our main goals on this stage:

[x] #5: provide the infrastructure: project template, build, CI, logging
[ ] #6: design the basic concepts that will be required for integration (tasks, task attributes)
[ ] #8: design the most basic concepts for multi-node support (I thought we could live without that for this milestone, but it looks like we won't able to)
[ ] #9: establish the data storage (the simplest one for further maintainership/migration)
[ ] #11: provide a Taskwarrior node (either via standard import/export mechanism or via the direct database read/write, preferably the former one)
[ ] #12: establish integration test process for the Taskwarrior import/export
[ ] #13: provide a simple UX (probably mimic the Taskwarrior one)
[ ] #14: full data backup and restore

Essentially, I want to start using Praefectus instead of Taskwarrior at least sometimes during implementation of this milestone.

Here's a list of non-goals to clarify a bit:

full multi-node synchronization
scripting
AI
even a little bit finalized UX
scheduling (outside of features that are already in the Taskwarrior)

ForNeVeR / praefectus

Minimum Viable Product #4