Hi everyone, I think Alex is proposing a solution to this current situation: 1) Someone encounters a problem with backintime, 2) they google around and find an open Github issue, 3) they read through the issue until they find a workaround that helps. As far as I undestand, Alex would like to create a "Known Problems and Workarounds" section somewhere (maybe in Github's README.md), so that people can find the "known workarounds to known problems" more easily. Is that right? Cheers, Michael On 18.06.2022 10:43, c.buhtz@posteo.jp wrote:
Dear Alex,
welcome the list and thank you for your thoughts.
On 2022-06-17 14:49 "Alex S." <alex4983@gmx.de> wrote:
The easiest (but still helpful) thing to start with, would be to update the documentation. The issues on github contain a lot of information, some of which should also be consolidated at one place, I think. [1] refers to a FAQ page and an external (readthedocs.io) page. I suggest to also create a page with a title like "Known problems" that can directly be found from [1].
I am not sure if I understand all this and maybe some things are mixed up here.
I assume with the term "documentation" you don't mean a user-guide or code-reference-guide. Correct? You mean something like a protocol or document with the known problems. Am I right?
Kind Christian