Task

A command-line incremental organization and coordination utility for task management, powered by Racket.

In alpha. Expect rough and sharp edges and breaking changes.

Installation and Setup

• Install some kind of terminal.
  On MacOS, use the terminal app.
  On Windows, Windows Subsystem for Linux is recommended.
• Install Racket 8.8+.
  Prior versions may work, but 8.8+ is confirmed to work.
• Clone this repository and git checkout setup/as-command and follow the instructions in that README. Run task-update release/alpha to install the program tracking the alpha branch.
  If you want a custom install, use the scripts laid out there as a guide.

Usage and Integration

Without using the default run script, run with racket main.rkt. The program is a command-line interface; ? or help will show available commands.

The data format was chosen so it works well with git, as long as all merges are done through rebases. Remember to pull datafile with git pull --rebase, or write yourself a script that does it; or use the script task-sync in the setup/as-command branch.

Configuration

You can interoperate among multiple organizations ("domains") by setting things up in the task.config file as such. For instance, if you have your own work, some planning you need to do within your family, and some coordination you need to do with your hobby group, you can set up the folder stucture as follows:

.
|- self
|  \- data.dat
|- family
|  \- data.dat
\- hobby
   \- data.dat

and configure task.config with

(domain :
    (datafile "self/data.dat")
    (login "me"))
(domain family:
    (datafile "family/data.dat")
    (login "<me>"))
(domain hobby:
    (datafile "hobby/data.dat")
    (login "<me>"))

When you start the program you'll be logged in to all three domains.

Furthermore, with all three domains in independent directories, they can be attached to separate git repositories shared with your respective groups.

Contributing

This repository has a sister repository racket-task-tracker which provides the datafile in this domain. I recommend setting it up with the instructions in the setup/as-command branch, as then you can test your changes just by running task-update <upstream-test-branch>.

All contributions to ideas, designs, bugfixes, minor UI improvements, and documentation are greatly appreciated; for the former two please open an issue, and for the latter three feel free to open a pull request.

For writing features, please feel free to open a pull request with a minimum viable product. New features need to be carefully integrated into the codebase, as there are still core features that need to be implemented.