Update repository topics

[lauft]

Your repository is listed on the Taskwarrior tools list, thanks for contributing! ❤️

We want to inform you about some changes to the crawler script collecting the tool information from GitHub:

Your tool is listed because it has the keyword taskwarrior among its topics.

With the release of Taskwarrior 3 and its changes to task synchronization, we want to improve the tool listings by showing whether it is intended for Taskwarrior 2, Taskwarrior 3, and/or Taskserver.

Your tools with topic taskwarrior will be listed on the tools page as intended for both, Taskwarrior 2 and Taskwarrior 3.
If this is correct, then there is nothing else to do – just close the issue. 🙂
However, if your tool is only working with Taskwarrior 2, we would ask you to update your topic to taskwarrior2 instead.

For further questions and details, you can go to this GitHub discussion.
Thank you very much for your support!

[RedEtherbloom]

If future development for only taskwarrior3 is planned, but the taskwarrior2 releases will stay available(and may receive bugfixes, if there are particularly bad ones) would the taskwarrior tag for 2 and 3 still be appropriate?
Or would that require actively supporting both versions in the future?

(fyi: new co-maintainer)

[lauft]

Or would that require actively supporting both versions in the future?

In a way, yes, I would say. When you have your tool listed for both, Taskwarrior 2 and 3, those users might come here and ask "why does it not work with my setup?"

As the switch from Taskwarrior 2 to 3 only affects the storage backend, AFAIK, you should be good with tag taskwarrior if you only rely on the CLI interface... 🤔

[kdheepak]

We currently only use the cli interface but may want to switch to taskwarrior3 alone in the future.

btw @lauft, do you have numbers or a sense for how many users still use taskwarrior2?

[lauft]

do you have numbers or a sense for how many users still use taskwarrior2?

No. That's a question for @tbabej or @djmitche, I assume...

[linuxcaffe]

Oh, the 20 year 800lb gorilla of cli task managers? Many?

…

On Wed., Nov. 13, 2024, 9:59 a.m. Thomas Lauf ***@***.***> wrote: do you have numbers or a sense for how many users still use taskwarrior2? No. That's a question for @tbabej <https://github.com/tbabej> or @djmitche <https://github.com/djmitche>, I assume... — Reply to this email directly, view it on GitHub <#588 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR6S64DHUZXTGAJMFEQRCD2ANSMJAVCNFSM6AAAAABJXXMC3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZTHA3DCNZTG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[tbabej]

We don't have any built-in metrics / reports, so beyond running a survey we don't know the actual versions users are on.

[RedEtherbloom]

We'd(plural) imagine that the transition to taskwarrior3 will probably take 2-4 years for a lot of users.
A lot of package managers are still on the v2 version.

Maybe we can keep v2 support for those e.g. two years. The biggest blocker would probably be the task implementation.
How well can taskchampions Tasks be manually constucted/imported? We'd like to avoid having to write a custom wrapper that switches between task-hookrs and taskchampion, depending on context.

[djmitche]

I'm not sure what that question means. Maybe it's worth giving it a try and seeing what problems arise? If you only use the CLI then there's probably no issue.