It’s almost done (it would take one or two weeks to clean it up for FOSS release). It’s a CLI tool. It works great for my use case, but I’m wondering if there’s any interest in a tool like this.

Say you have a simple time-tracking tool that tracks what you do daily. The only problem is that there are gaps and whatnot, which might not look nice if you need to send it to someone else. This tool fixes pretty much all of that.

Main format is a JSON with a “description”, and either “duration” or a “start”/“end” pair. It supports the Timewarrior format out of the box (CLI Time tracking tool).

  • delirious_owl@discuss.online
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    2 months ago

    I just say I worked X hours per day, above my log entries describing what I did that day. Why do they need anything more than that?

    • naeap
      link
      fedilink
      arrow-up
      4
      ·
      2 months ago

      Sometimes I work on a larger project that is split up in different sub projects, that were sold separately and are maybe paid by different departments. So I need to at least spilt those up.
      Also it’s often easier to follow what exactly was done, when I differentiate more between my tasks and not just put a collective line there - just like small commits are more helpful than one large one.

      But maybe I understood you wrong…?