Closed jenshannoschwalm closed 2 years ago
I'm fine with most of your suggestions, though I'd prefer to keep the manual as a fairly formally-styled document so we'll find some other term than "nerds tuning" :)
With the new documentation, it's pretty easy to run a copy of the website from a local repo if you need to test so PRs are fine (see the README and https://darktable-org.github.io/dtdocs/en/special-topics/contributing/). Perhaps propose something rough to start out with, either as a PR or a separate document, describing what you intend in more detail. There's been so much going on with these perf settings recently I don't have the first clue how they work, so perhaps a good starter would be a basic summary of what's changed since v3.8.
Whatever you propose will always go through a copy-edit from me either as part of your PR or shortly after it's merged. I'm happy to adapt to whatever way of working would be easier for you.
Here is a first part of my "suggested docs", what do you think? mem-management.odt
Looks good for a first draft. Will probably make more sense once I see the geeks-eye-view as well :)
Just a note, I am currently investigating a rather obscure opencl problem (sometimes leading to hanging dt) so documentation is unfortunately delayed until that bug is resolved...
Ok, the bug was not a bug but an installation problem on my side mismatching kernel & nvidia stuff.
Here is another version of the file, this time i added technical information about resourcelevel setting. Are you ok this way? mem-management.odt
Here is
@elstoc (and all people interested in the docs) this is somewhat demanding, first some general ideas
What approach would you prefer? Would you want me to write all docs as plain ascii and you modify the git repo? Or some pr's - (as i don't generate the docs myself and rely on the auto generated they might have errors you need to fix later) ?