task

creates a plain-text task file in the current directory
git clone git://brookjeynes.dev/bjeynes/task.git
Log | Files | Refs | README | LICENSE

commit 9c1ba05da7e23ac3c9c02ed3b9e9e7722acdcefc
parent 09b96240c65024be404eef777d84d79772463681
Author: brookjeynes <me@brookjeynes.dev>
Date:   Thu, 11 Jun 2026 16:43:12 +1000

docs: make license attribute more clear for both repo and manifesto.txt

Diffstat:
ALICENSE | 14++++++++++++++
AREADME | 21+++++++++++++++++++++
Mmanifesto.txt | 33++++++++++++++++++++-------------
3 files changed, 55 insertions(+), 13 deletions(-)

diff --git a/LICENSE b/LICENSE @@ -0,0 +1,14 @@ +BSD Zero Clause License + +Copyright (c) 2026 Brook Jeynes <me@brookjeynes.dev> + +Permission to use, copy, modify, and/or distribute this software for any +purpose with or without fee is hereby granted. + +THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH +REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY +AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, +INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM +LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR +OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR +PERFORMANCE OF THIS SOFTWARE. diff --git a/README b/README @@ -0,0 +1,21 @@ +task +==== + +task creates a plain-text task file in the current directory. + +Build: + + make build + +Usage: + + task "Call Mom" + task -p A "Call Mom" @phone +family + +The task title becomes the filename. Spaces, slashes, backslashes, and leading +dots are replaced with underscores. + +If VISUAL or EDITOR is set, task opens the new file in that editor. + +Code is licensed under 0BSD. manifesto.txt is adapted from todo.txt and is +distributed under GPLv3: https://www.gnu.org/licenses/gpl-3.0.html diff --git a/manifesto.txt b/manifesto.txt @@ -21,18 +21,18 @@ There are three key axes to an effective todo list associated with it. Your system should be able to list out all the tasks specific to a project. - In order to move along a project like "Cleaning out the garage", my task list - should give me the next logical action to take in order to move that project - along. "Clean out the garage" isn't a good todo item; but "Call Goodwill to - schedule pickup" in the "Clean out garage" project is. + In order to move along a project like "Cleaning out the garage", my task + list should give me the next logical action to take in order to move that + project along. "Clean out the garage" isn't a good todo item; but "Call + Goodwill to schedule pickup" in the "Clean out garage" project is. 3. Context - Getting Things Done[1] author David Allen suggests splitting up your task lists - by context - ie, the place and situation where you'll work on the job. Messages - that you need to send go in the '@email' context; calls to be made '@phone', - household projects '@home'. That way, when you've got a few minutes in the car - with your cell phone, you can easily check your '@phone' tasks and make a call - or two while you have the opportunity. + Getting Things Done[1] author David Allen suggests splitting up your task + lists by context - ie, the place and situation where you'll work on the + job. Messages that you need to send go in the '@email' context; calls to be + made '@phone', household projects '@home'. That way, when you've got a few + minutes in the car with your cell phone, you can easily check your '@phone' + tasks and make a call or two while you have the opportunity. [1] URL:https://en.wikipedia.org/wiki/Getting_Things_Done @@ -113,8 +113,8 @@ Rule 2: Project and context may appear AFTER the title. Rule 3: Additional context may appear on the 3rd line of the file onwards. - A task does not have to have additional context. If it does, it should be on - the 3rd line of the task file. + A task does not have to have additional context. If it does, it should be + on the 3rd line of the task file. This task has additional context (A) checkout race condition @bug +checkout @@ -130,4 +130,11 @@ that have not been finished sit flat-file in the tasks/ folder. There is no concept of "in-progress", a task is either done or not-done. -<modified from todo.txt [https://github.com/todotxt/todo.txt]> +Attribution +----------- + +This document is adapted from todo.txt: https://github.com/todotxt/todo.txt + +The original todo.txt format documentation is licensed under the GNU General +Public License v3.0. This modified version is distributed under the same +license: https://www.gnu.org/licenses/gpl-3.0.html