I believe it would be relatively simple to calculate time locally and then display the totals in some custom Atom buffers.
You can actually configure a .koala file in the root of your project to define what to send to Koala.
Nevertheless, I see your point. I'm thinking of going open source and releasing a community edition so you can set-up a hosted version. Would that be interesting for you?
Sweet, I didn't realise that. A self-hosted version would be cool. For my own projects I don't mind sending data, just for corporate work its more difficult. Having something I could run on my own machine and periodically get reports from without having to manually enter time constantly would be really handy.
Having had a very quick browse on the page. This looks like wakatime.com.
I've been using that one for a couple of months with zero problems, it gives me an very detailed overview of what I worked on (down to filename, h:m:s editing, git branch name etc) and it gives me daily and weekly summaries.
Is there a reason for me to change to koala?
- When I go to pledge/api docs I see previously hidden navbar links 'events', 'reports'
- If I enter the 'events' section, it asks me to sign in and the browser history back action stops working.
I'm really impressed by the pledge you're making there, it's a very amicable touch.
Regarding the pledge: it's actually something I've been seeing at more startups. I can't recall which one but I should put up a link to them.
