Possible Feedback On Time Tracking CLI Implemented In Rust

Hey Sebastian,
fellow Berliner and `gitoxide` fan here :)

I'm currently working on an activity tracking (and hopefully a future task, project, and time management tool) written in Rust. Some time ago, I was looking at your time sheets and found it impressive to have this level of transparency. For some future self-employment, I wanted to create a CLI activity tracking tool. It's called [`pace`](https://github.com/pace-rs/pace) and is on [crates.io](https://crates.io/crates/pace-rs):



Currently, it's at the stage, where the base activity tracking and reporting is implemented (although I still need to implement the output to `csv`, which will come soon. `json` output of a review summary is already supported).

Some future vision for `pace` in short

- implement HTML templating for `review` so people can export their activity logs to their own (and a premade) HTML template and print it as pdf, also they could create bills for customers like that (additional functionality for billable activities would be as easy as adding a new optional struct field to the activity log)

- create a `pace-server` after implementing logging to `SQLite` so people could use pace on different devices and essentially self-host

- implement task and project management file based first, so pace would create a `projects.pace.toml` in a directory root and then people could create multiple `tasks.pace.toml` in lower directory hierarchies that reference the root `projects.pace.toml` to have hierarchical tasks for e.g. monorepositories

- based on the implementation of `tasks` we can then add pomodoro and other workflows

- Pomodoro requires a longer running process, so here it would be essential to implement a small GUI like `work-break` did, more like a notification pop-up that is able to handle the pomodoro sessions


- afterwards it would be nice to expand support from individual use to team collaboration

I wonder if you would be able to test `pace` a bit and give some feedback from your perspective and use cases, so I can improve it. I think that would be really valuable to me. As I wrote it for people like you (and me).

Until then, and thank you for your work on `gitoxide`,
Simon