My inclination would be to keep the wiki pages as the "development
branch" for which the Reports chapter is the "release branch".
Suggestions for improvements could be tried out in the wiki with lower
friction. When the wiki contents represents a significant improvement
over the Reports chapter, migrate the content to the Reports chapter.
By the same token, sections of the Reports chapter can have links to the
corresponding Wiki page.
MusicBrainz uses a scheme like this. Compare this documentation page
http://musicbrainz.org/doc/Style/Artist_Credits/Featured_artists
with the corresponding Wiki page:
http://wiki.musicbrainz.org/Style/Artist_Credits/Featured_artists
--Jim DeLaHunt, Vancouver, Canada
On 2017-01-15 20:48, David T. via gnucash-devel wrote:
Hello,
I will start by saying: “Yes, I know it’s a wiki…”
However, now that the Reports chapter (which incorporates nearly all the Wiki
reports information verbatim) is officially available as part of the normal
Documentation distribution, I propose removing this information in the wiki,
and adding a note to say that the wiki information has been moved to the
Tutorial and Concepts Guide as of GnuCash 2.6.15.
As this is rather a substantial amount of information that will go away from
the wiki, I thought it best to double check in the community before acting.
Cheers,
David
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
--
--Jim DeLaHunt, j...@jdlh.com http://blog.jdlh.com/ (and jdlh.com)
multilingual websites consultant. GnuCash 2.6.11 on MacOS X 10.10.
157-2906 West Broadway, Vancouver BC V6K 2G8, Canada
Canada mobile +1-604-376-8953
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
