From 636862f8c5606bb9969c6bbeea8182c9a2e3ccc4 Mon Sep 17 00:00:00 2001 From: "Dustin J. Mitchell" Date: Wed, 13 Oct 2021 17:59:58 -0400 Subject: [PATCH] update README with current relationship to TW --- README.md | 18 ++++-------------- 1 file changed, 4 insertions(+), 14 deletions(-) diff --git a/README.md b/README.md index a4582257e..10e119460 100644 --- a/README.md +++ b/README.md @@ -9,21 +9,11 @@ See the [documentation](https://taskchampion.github.io/taskchampion/) for more! ## Status -TC is still under development. -You are welcome to [help out!](https://github.com/djmitche/taskchampion/blob/main/CONTRIBUTING.md). -Even if you just want to get some practice with Rust, your contribution is welcome. +TaskChampion currently functions as a "testbed" for new functionality that may later be incorporated into TaskWarrior. +It can be developed without the requirements of compatibliity, allowing us to explore and fix edge-cases in things like the replica-synchronization model. -Since development of TaskChampion began, TaskWarrior developers have resumed work and made several releases. -Assuming that continues, it is unlikely that TaskChampion will ever be recommended for day-to-day use, as that would only serve to split the TaskWarrior community. - -## Goals - - * Feature parity with TaskWarrior (but not compatibility) - * Aproachable, maintainable codebase - * Active development community - * Reasonable privacy: user's task details not visible on server - * Reliable concurrency - clients do not diverge - * Storage performance O(n) with n number of tasks +While you are welcome to [help out](https://github.com/taskchampion/taskchampion/blob/main/CONTRIBUTING.md), you should do so with the awareness that your work might never be used. +But, if you just want to get some practice with Rust, we'd be happy to have you. ## Structure