Rename Repo Tracking

[josehbez]

Hey @kamilprusko and @codito ,

I'm currently rewriting the tracking utility to make it completely framework-agnostic:

The main reason for this refactor is to support multiple frontends (sources) and plugins (destinations):

Frontends (Sources):

• gnome-pomodoro (legacy) - custom actions
• focus-timer (beta) - automation
• CLI
• Any other...

Plugins (Destinations):

• Odoo
• Toggl
• Clockify
• Any others ..

I also have a couple of ideas for the repo name, such as TimesheetSync or TimerSync.

Please let me know your thoughts or if you have any advice on this approach.

[kamilprusko]

Hi @josehbez

I do not think it's worth keeping support for the old app. Existing users of gnome-pomodoro-tracking can keep using it. I see what you're trying to do - to keep the continuity and the familiar workflow.

Important note: The automation panel in the new app is not available on Flathub due to extra permissions needed... The Flathub reviewer didn't like the idea of a pomodoro timer having access to the commandline. So, not all users will have it. Automation panel could be published as an Add-Ins/Extensions.

Let's step back and assess the current pain points... In my opinion, they are:

1. many users are not aware of the project
2. setup may be too technical for some
3. tokens are not stored in a secure way.

Ideally, I see it included in the app. In main branch has landed integrations panel and a proper architecture for plugins (based on libpeas). Quick mockup:

Mockup SVG

We would require use of Secret portal to store credentials and a permission for network access. I doubt Flathub reviewers would approve it 😓 ... so, for now for now we could instruct advanced users to install the app from source, or to distribute Flatpak bundle on our own.

The tagging and naming current Pomodoro could be added to the state selector.

Additional benefits of including into the app could be offline support and ability to upload historic entries.

@josehbez What do you think?