Documentation

[David Carlson]

On 1/7/2014 12:11 AM, David wrote:
> John,
>
> I began looking through these bugs. The first covers documentation for GnuCash 1.7, and is assigned to Chris Lyttle. I don't recognize the name; would someone take a look at the bug ( https://bugzilla.gnome.org/show_bug.cgi?id=98292) and see whether it can be closed, as I believe it probably could?
>
> Thanks,
> David
>
>
>
> _____________________________________________
> From: John Ralls <jralls at ceridwen.us>
> Sent: Tue Dec 10 10:40:08 PST 2013
> To: GnuCash development list <gnucash-devel at gnucash.org>
> Subject: Documentation
>
>
> As we get down to the wire for releasing GnuCash 2.6, we still have 45 open documentation bugs. You can see the list at http://tinyurl.com/q6y4jvt; each bug on that list is a clickable link to the details.
>
> If you’ve been looking for a way to contribute to Gnucash (or even if you haven’t ;-) ) but can’t contribute code for whatever reason, working on the documentation would be an excellent way to help.
>
> Following the Gnome practice we use DocBook. Gnome has a nice manual for writing documentation, including DocBook, at https://developer.gnome.org/gdp-handbook/stable/. 
>
> Regards,
> John Ralls
>
>
> _____________________________________________
>
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

I think that either there was documentation added for the use of trading
accounts or maybe I am remembering the thorough documentation that
justified their existence when they were created.  In either case, I
would conclude that this bug could be closed. 

If anyone wants further details, they are definitely free to ask. 

I am still mulling over some bugs that I have started and I am not ready
to work on others until I have polished those up in the light of recent
suggestions and re-submitted them.

I want to congratulate the developers on their great efforts in the last
quarter of 2013.  I also want to note that when a lot of work is done,
as there was in the process of releasing 2.6.0, there is an increased
probability that some bugs will slip through. The only way to avoid all
mistakes is to do nothing at all.

David C