Bug 633590 - Document the GnuCash Reports

[David T.]

John,

Thanks for the information; being so new to this, I was unsure as to whether I had in fact succeeded in getting this moving through the pipeline. [There was a moment, for example, that it looked like my pull request had no data in it all (I suspect it had something to do with commitment…).]

David

> On Oct 21, 2016, at 7:01 PM, John Ralls <jralls at ceridwen.us> wrote:
> 
> 
>> On Oct 21, 2016, at 6:19 AM, David T. via gnucash-devel <gnucash-devel at gnucash.org> wrote:
>> 
>> Hello,
>> 
>> I am posting here to alert developers that I (believe) I have made a pull request to have Bug 633590 addressed. Since the reports section of the wiki has been largely filled in, I was able to finally take that information and migrate it over to ch_reports.xml, edit it, and format it for the Guide. The changes are pretty substantial, consisting as they do of descriptions of almost all the standard reports. I followed procedure though (I believe), and I think the information is valid both in content and format.
>> 
>> There were a number of gaps, some of which I was able to fill in, others (such as the Budget reports and some Business reports) I left empty. I believe that pushing forward with what is there is preferable to waiting another 6 years for someone to come along and fill in those remaining gaps (I did make a request on the lists regarding the Budget reports, without response).
>> 
>> Please take a look and let me know if further needs to be done. Bear in mind that if it involves Git, you’re probably going to have to hold my hand through it.
>> 
> 
> David,
> 
> No need to report PRs to the list, Github sends email to the developers whenever a PR is created or modified. Thanks for the work!
> 
> Regards,
> John Ralls
> 
>