GothenburgBitFactory/taskwarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/taskwarrior.git synced 2025-06-26 10:54:26 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
taskwarrior/doc/devel/rfcs
History
Exact
Matthew 3ae7413ebd
Update task.md json lines end with \n (0xA) not \r (0xD) (#3752) 
Update task.md to fix mistake in json format.  In the code the json lines end with \n (0xA) not \r (0xD)
2025-02-01 15:37:43 -05:00
..
cli.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
client.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
dom.md add initial bulk run from pre-commit over all files 2024-07-29 22:34:51 +02:00
plans.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
protocol.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
README.md Fix typo 2023-10-20 12:03:02 +02:00
recurrence.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
request.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
rules.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
sync.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
task.md Update task.md json lines end with \n (0xA) not \r (0xD) (#3752) 2025-02-01 15:37:43 -05:00
workweek.md Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00
year.png Consolidate in-repo documentation (#3143) 2023-08-09 21:30:01 -04:00

README.md

Taskwarrior RFCS

In the mid-2010's, Taskwarrior development was organized around RFCs, as a way to invite comment before designs were finalized. Although these documents were less formal than IETF RFCs they serve a similar purpose. In more recent years, use of RFCs has been discontinued, and the documents linked here should be considered historical. Many were never completely implemented.