Hi David, starting from the accessability, I think the practial persistence is as follows: IRC < email < wiki:FAQ < wiki:theme_page < docs
Examples: Geert or John explain me something in IRC and I am pretty sure I will need it next year again, I copy it in a page below Project_Administration, Coding_Style, or wherever it belongs. Sometimes I am tired to explain the same content on the mailing list (or IRC) again and again. If a page for the theme exists in the wiki, I update the page, else add a section to the FAQ. >From time to time one can go through the wiki and move te content of related questions into a thematic page, replacing the FAQ content by links. I think also, the wike is a good place for cooperative developemet of articlesd. Finally this thematic pages should become incorporated in the docs. The program should not require an internet connection, so links to the wiki are not nice. Most users get the docs together with the program installed. Frank Am 10.04.20 um 01:08 schrieb David Cousens: : > The other obvious thing is to update the documentation with appropriate > instructions and in the shorter term put this up on the wiki in the > meantime. I don't know if it is legit or desirable to reference a wiki page > from the documentation or even from within the program (in the warning > popups for example) but this may be a temporary way to alert users and point > users to a solution until an autofix procedure can be developed. : _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
