![](https://seccdn.libravatar.org/avatar/28fb60f36a5c05d6e95d00be1c0c257c.jpg?s=120&d=mm&r=g)
Le 08/08/2021 à 16:58, Stefan Seyfried a écrit :
On 08.08.21 15:34, jdd@dodin.org wrote:
In a doc, there should not be any "context specific" that is not immediately obvious, so you can change it asap.
One example: You document a workaround to get something working (let's say your bluethooth adapter). One year later, I come around and find that I do not need your work around to get bluetooth working. But was it fixed over time or is it just that my (slightly different) hardware does not nee the workaround yours needs?
why??? simply add the info near the doc
The easiest way would be to ask the original author of the hint.
certainly not, most probably he don't remember having done so :-) Personally, I think the discussion pages are a horrible way to report
bugs in a page.
you see... you think like a developer... changing something in a documentation page have nothing to do with a bug. It do not expect any change elsewhere Does one even get notified if someone writes something
on a discussion page? And how?
AFAIK you can "follow" a page if you want.
time into documenting stuff on wikis. Having to use bad tools makes me avoid the work that should be done. So simple.
Now I am mostly a developer type of guy, means: I don't really need that documentation. If something does not work, in the worst case, I just look up the problem in the source code ;-)
good luck if you have to look in libreoffice or firefox code :-(
my $HOME folder. In the not-so-bad case, I write about it on my blog
where you are sure nobody will find it, for sure... writing doc is a work on itself. I won't say nothing about the way you have to write your code, but I write docs for 50 years now :-) jdd -- http://dodin.org