Add users and metadata to tracked entries

[jdudek]

Store name and email of current user taken from the config.

Allow setting other metadata, like current task name. The task name could be passed via on option to muon commit/stop or set permanently using other commands. For example:

muon commit 10:00 10:15 -t "doing magic"

muon start
muon stop -t "doing magic"

muon task start "doing magic"
muon task # prints "doing magic"
muon start
muon stop
muon task finish

We should consider support for arbitrary metadata for entries (and/or for tasks), to allow setting - for example - Redmine ticket number or whether tracked hours are billable.

[paneq]

How about muon start key:value key:value like

muon start task:add coments to blogposts ticket:#123

I am not sure about syntax. Maybe
muon start "task: add comments" ticket:#123

I would prefer not having to use "" when I need to use space character. I way more often need to use spac than :.

I am not sure about muon task. Because when I want to start again working on the same task I could use my shell autocomplete to quickly invoke muon start with identical command options. What do you think ?

[jdudek]

I like the idea of specifying multiple fields and leaving freedom of choosing them to the user.

I am not sure about muon task. Because when I want to start again working on the same task I could use my shell autocomplete to quickly invoke muon start with identical command options. What do you think ?

I want to be able to start/stop time tracking quickly (I use aliases muon a, muon z all the time), so I think the ability to keep metadata across multiple commits is essential.

Maybe task is not perfect name if we allow any fields to be set, but I think setting "tasks" will be primary use case, so I don't really know...

muon start "task: add comments" ticket:#123
I would prefer not having to use "" when I need to use space character. I way more often need to use spac than :.

Actually you should escape ticket:#123 as well, because shell may interpret # as comment ;-)

IMHO quotes are OK, I assume setting metadata won't happen more often than committing in Git.

[paneq]

I think our both approaches are ok.

So task command is like setting multiple key:value for following start / stop time records ? But they could also be set via start command ? If so, then I like the idea :)

Would be good if start display those values so that if there is something remembered via task I would see it a remain sure that proper task is being tracked.

[paneq]

How about muon session instead of muon task ? I believe the semantics of this command are similar to session in browsers or session in testing. As something that constitutes multiple actions...

Hit or Kit ?

If session were given a name or unique id, we could even come back to them at any time. Like named sessions in screen :)

[jdudek]

So task command is like setting multiple key:value for following start / stop time records ?

Exactly.

But they could also be set via start command ? If so, then I like the idea :)

Right, this is the idea, but it will probably be via stop command.

Would be good if start display those values so that if there is something remembered via task I would see it a remain sure that proper task is being tracked.

We should definitely do this ;)

I'm not sure about muon session yet ;)

[paneq]

Take your time and you will love muon session :)