Update README.md
try to explain the intentions of the fork
This commit is contained in:
@@ -19,8 +19,13 @@ features](https://taskwarrior.org/docs/), developed as a portable open source pr
|
||||
with an active and quite vast [ecosystem of tools, hooks and
|
||||
extensions](https://taskwarrior.org/tools/).
|
||||
|
||||
### HEADS UP! THIS FORK HAS BEEN ESTABLISHED TO MAINTAIN AND DEVELOP THE TASKWARRIOR 2.6.X BRANCH!!
|
||||
It may fall behind of taskwarrior3.x (taskchampion) development, but will a place for fixes and cherry-picking from changes made after official 2.6.2 releases.
|
||||
### HEADS UP!
|
||||
### This fork is to intended to preserve the taskwarrior 2.6.2 codebase, and to allow for further fixes and improvements!!
|
||||
It's great to see that taskwarrior is still an active project and the active developers have a vision that fuses taskchampion and an SQL database. It's cool, and in rust, and everything..
|
||||
|
||||
.. but it was the fact that task used a text-file to store data, that first hooked me to the project, and I am almost certainly first taskwarrior user, I'm technically the original taskwarrior Designer! I worked with the orginal programmer, Paul Beckingham, as he brilliantly implemented so many of my crazy ideas, like colors, urgency, reports, UDAs, attribute modifiers and SO much more!
|
||||
|
||||
Because I'm set im my ways like that, and kind of squeamish about keeping my task data as a SQL database, this repo is somewhare I can try to apply fixes and cherry-pick from changes made after official 2.6.2 releases, and to curate some of the things that I think belong with it. That said, I'm a terrible programmer, a dubious developer, and would welcome input and contributions.
|
||||
|
||||
## Install
|
||||
[](https://archlinux.org/packages/community/x86_64/task/)
|
||||
|
||||
Reference in New Issue
Block a user