Lyz

Hi @StefanoCecere thanks for taking the time to open an issue. So far it's not possible to do what you want with `mkdocs-newsletter`, sorry :(. I'm afraid that even though...

Timewarrior as far as I remember (from the time I've implemented [timing support for taskwarrior](https://github.com/robgolding/tasklib/pull/55)) relies on adding annotations to the tasks through hooks. Which I feel is a not...

Looks good! When the time comes, we'll definitely evaluate the integration of timewarrior instead of rewriting everything from scratch. Each approach has it's advantages and inconveniences. Thanks for the tip

Implement an [Audit table](https://lyz-code.github.io/blue-book/architecture/database_architecture/), to extract which fields are changed, use something like [DeepDiff](https://zepworks.com/deepdiff/5.0.2/)

Dependencies help you define relationship between tasks to block or release them given the state of other tasks. Serial tasks, as I see them, will solve another problem. The division...

Maybe it's interesting to have a new `Task` attribute called `import_id` so we can make the import process idempotent

Some ideas of how to implement it are available in [this ADR](https://lyz-code.github.io/pydo/adr/0xx-agenda/)

Hi @ggoretkin-bdai thanks for taking the time to open an issue. Maybe I'm understanding you wrong but the snippet you provided is not a valid yaml way to break long...

The `>` to `>-` is not a big deal because it's always best not to have the `\n` at the end of the string. I can reproduce the long line...

Hi @lucatortiglione thanks for taking the time to open the issue. Sadly since the start of the year [I'm not maintaining the project for the moment](https://github.com/lyz-code/yamlfix/issues/272) so I'm not going...