Replies: 4 comments 4 replies
-
I actually tried to rewrite Taskwarrior from scratch -- https://github.com/taskchampion/taskchampion. There were reasons not to do so that have been discussed other places, but it illustrates at least some of my answers to these questions. At the moment, Taskwarrior's in a bit of a slow spot -- there just aren't enough devs working on it to make measurable progress (one dev can't review their own PRs!). So I think your first question is probably the most important: how would we get a "critical mass" of people involved? |
Beta Was this translation helpful? Give feedback.
-
I haven't been using Taskwarrior for long, but I really like it. There's a lot thought in it's design. For example: being able to write hooks in any language is very useful. The main obstruction for me contributing is The parts that work well with other languages (or language-agnostic) have been really useful - hooks, Python unit tests, tasklib, rfcs, docs. It would be good if Taskwarrior provided a core library that could be used to build |
Beta Was this translation helpful? Give feedback.
-
Oh. Neat. I see Taskchampion use Rust. That is something I am really keen to learn in near near future. Unfortunately C is not on my radar. |
Beta Was this translation helpful? Give feedback.
-
There are a few rust-tagged issues in this repo if you'd like to get your feet wet ;) |
Beta Was this translation helpful? Give feedback.
-
I know this most likely will be unpopular idea, but still...
No software is perfect.
Over time we realize that we took not the best paths to build it.
It would be beneficial for the community to learn from the other mistakes.
What would be those things you would do differently if you would decide to
write Taskwarrior from scratch?
For example:
Beta Was this translation helpful? Give feedback.
All reactions