Add time pools

[snehal-shekatkar]

Add time pools

[dathanb]

Thanks @ryneeverett , that's definitely what I meant. A lot of this can be done right now with the hooks that Taskwarrior already supports. e.g., if you assume X hours of time available per work day, and have a UDA representing the amount of hours a task is going to take, a hook that would reject (or warn on) task additions or modifications that violate time pool limits wouldn't be too hard, which IMO speaks well of taskwarrior.

What I don't think would be so easy to do through taskwarrior would be things like custom reports based on time pools. You could task execute <report name> to invoke the external app to run the report, but the external app would be have to fetch the relevant information itself -- so I think there's more Taskwarrior could do to help there. e.g., an extension protocol that would let taskwarrior provide relevant task data (e.g., based on current context and/or command line filters) to the external app; similarly it'd be helpful for Taskwarrior to pass config information to the external app so extensions can lean on taskwarrior for configuration instead of having to manage its config entirely itself.

IMO, treating this use case as a set of requirements or feature requests for taskwarrior extensibility and trying to enable a rish extension ecosystem would be a better long-term approach for taskwarrior than adding this specific case as a core feature.

(Caveat: I'm not a taskwarrior maintainer or part of the team, just a fan, so I'm definitely not speaking on behalf of the taskwarrior team here.)

[dathanb]

This should be largely doable in an external app via hooks, I think.

[snehal-shekatkar]

This should be largely doable in an external app via hooks, I think.

Perhaps a guide to doing that could be added then? I really think that this is an extremely important thing to consider in the roadmap.

[ryneeverett]

@snehal-shekatkar It seems like you may be misreading "largely doable" as "trivial". I think @dathanb is suggesting that an app would have to be developed which may be relatively straightforward but not a trivial amount of work.

[snehal-shekatkar]

@ryneeverett Thanks for the clarification. I thought @dathanb was talking about using Timewarrior.