Properties

Last built 1 year ago using go version go1.6 linux/amd64 and 45 seconds of time

Downloads
Filename
File Size
 
minion_master_darwin-386.zip
643KiB
minion_master_darwin-amd64.zip
677KiB
minion_master_linux-386.zip
647KiB
minion_master_linux-amd64.zip
685KiB
minion_master_linux-arm.zip
645KiB
minion_master_windows-386.zip
681KiB
minion_master_windows-amd64.zip
722KiB
Project-Readme for this version

minion Join the chat at https://gitter.im/HaMster21/minion

:wrench: Work in progress task management

wercker status GoDoc Go Report Card codebeat badge codecov.io

Poor mans attempt to build something like Taskwarrior, but less restrictive and with Windows support

Goals

Tasks are difficult to handle for humans and everyone seems to handle them differently. I want minion to be flexible, so I try to provide and interface to let minion do its work and implement some defaults that can be tweaked individually.

My minion should be a commandline tool that helps me structuring my work. As such, it is intended to be a single person, local machine application without a fancy GUI.

Assumptions

I will assume that there are two kinds of structures that my minion will handle: Items and Collections thereof.

An Item can be something like a task, a habit, a note, a checklist entry or whatever. By default it will be stored as a plain text file, so it can be easily manipulated by anybody else. Every Item has (at least) the following fields:

  • Heading
  • Description
  • Collection it belongs to
  • Position in the collection, for ordering
  • Creation date/time
  • Last change date/time
  • Additional information, which is a key-value store of whatever you want

A Collection contains Items and adds ordering and a name to them. A collection has (at least) the following fields:

  • Name
  • Creation date/time
  • Last change date/time
  • Archive flag, to exclude it from being rendered as active
  • Archive date/time

Roadmap

  • Task and Collection interfaces
  • Reading/Writing tasks from/to JSON|TOML|Markdown|Textile|AsciiDoc
  • TermUI Dashboard
  • Output customization with go templates
  • Item and Collection hooks that get triggered on events in the Item/Collection
  • Storage backends other than the file system, like git (e.g. like git-appraise) or Redis or whatever
  • rkt/docker image to keep items and collections in a single container