General questions on current project status and how to help #349
-
Hello! 👋 This project caught my attention after seeing it mentioned in the Taskwarrior IRC. I have some questions, as the project seems quite interesting and I'm seeing how I can help:
I don't mean to impose by asking all these questions (as I understand that this may require effort to address - especially issue management, or finding work to assign to new contributors), but since I really enjoy the whole concept behind taskwarrior and have been burned several times with some of the issues it has, this seems like an interesting project to contribute to, and I want to help out. I am also learning Rust (and am enjoying it a lot) so this seems like a great opportunity to put what I have been learning to the test :) Edit: I have since found #52 which gives a recent(?) update on the state of things. Still unsure how to best help, and would appreciate any light that can be shed on this :) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Hey, welcome! TaskChampion has been through a few significant changes in direction, so yeah -- things are a bit confusing. Sorry about that! No, TC and TW have completely different sync backends. At the moment, my plan is to integrate TC into TW as the "core" -- handling task storage and sync -- with the existing CLI support remaining in place. That basically means the I think the "critical path" bits right now are best identified as the 0.5.0 milestone. #384 in particular might be a nice first bug. If you can work on that, make a comment and I'll assign it to you -- it's only assigned to me because I intended to do it soon (and assigned issues show up in my taskwarrior task list!). In general, the bits that need to be attended to soon are:
Does any of that sound particularly interesting? The server has some web-related Rust, the interface to TW involves a bunch of Rust FFI and C++, the CLI involves lots of |
Beta Was this translation helpful? Give feedback.
Hey, welcome!
TaskChampion has been through a few significant changes in direction, so yeah -- things are a bit confusing. Sorry about that!
No, TC and TW have completely different sync backends.
At the moment, my plan is to integrate TC into TW as the "core" -- handling task storage and sync -- with the existing CLI support remaining in place. That basically means the
taskchampion
and taskchampion-lib` crates, and not the CLI crate. That said, once that merger is complete, it'd be possible to sync between the TC CLI and the TW CLI, so it might be useful anyway! What I'd say right now is this: the CLI is not currently on the "critical path" that I'm working on, but you're right that havin…