about summary refs log tree commit diff
diff options
context:
space:
mode:
authorProfpatsch <mail@profpatsch.de>2023-01-07T14·03+0100
committerProfpatsch <mail@profpatsch.de>2023-01-07T15·21+0000
commite3c198161960ffe25be4c88a6b0277c41a95d817 (patch)
treefacaf2c0bd5f0ee0db53f7904a631910c37e38f5
parent727e6d890cad830c10c420f500583ebbed385d8a (diff)
docs(users/Profpatsch): notes for a tagtime reimplementation r/5628
Change-Id: I2c225a9f023b8694c292f4fb962b88db6e3cce07
Reviewed-on: https://cl.tvl.fyi/c/depot/+/7795
Reviewed-by: Profpatsch <mail@profpatsch.de>
Tested-by: BuildkiteCI
-rw-r--r--users/Profpatsch/tagtime/README.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/users/Profpatsch/tagtime/README.md b/users/Profpatsch/tagtime/README.md
new file mode 100644
index 0000000000..ab2c7d14e5
--- /dev/null
+++ b/users/Profpatsch/tagtime/README.md
@@ -0,0 +1,18 @@
+# tagtime reimplementation
+
+What’s great about original perl tagtime?
+
+* timestamps are deterministic from the beginning (keep)
+* the tagging system should just work (tm)
+
+What’s the problem with the original perl tagtime?
+
+* it uses a bad, arbitrary file format -> sqlite3
+* the query window does not time out, so it’s easy to miss that it’s open (often hidden behind another window), and then the following pings might never appear)
+* There’s a bug with tags containing a `.` -> sqlite3
+
+What would be cool to have?
+
+* multi-entry mode (ping on phone and laptop and merge the replies eventually since they will apply to single timestamps)
+* simplifying reporting based on fuzzy matching & history
+* auto-generate nice time reports with hours for work items