As we are already there,
one of you Davids might also review
https://github.com/Gnucash/gnucash/blob/maint/README section overview,
and probably files in
https://github.com/Gnucash/gnucash/tree/maint/doc
https://github.com/Gnucash/gnucash-docs/blob/maint/gnucash-docs.spec.in
...
which borrow the
If an attacker guesses the path a -Indexes directive won’t stop him from
requesting the directory from the server. It should return a 403 if there’s no
index.html, but perhaps there are servers out there that fail, or perhaps the
web design folks think that a blank page is better than a 403.
Of
> On Sep 15, 2018, at 5:29 AM, Frank H. Ellenberger
> wrote:
>
> As we are already there,
>
> one of you Davids might also review
> https://github.com/Gnucash/gnucash/blob/maint/README section overview,
>
> and probably files in
> https://github.com/Gnucash/gnucash/tree/maint/doc
> https://
Since John indicated there is not an effort to adhere to the current Gnome HIG,
that statement should probably be removed. (as they don’t conform any longer)
But there are a few places where I think they can be simplified, particularly
some items in the Actions menu should probably be moved to T
> On Sep 15, 2018, at 12:55 PM, David T. via gnucash-devel
> wrote:
>
>
>
>> On Sep 15, 2018, at 5:29 AM, Frank H. Ellenberger
>> wrote:
>>
>> As we are already there,
>>
>> one of you Davids might also review
>> https://github.com/Gnucash/gnucash/blob/maint/README section overview,
>>
That sounds like program development. I only do documentation.
> On Sep 14, 2018, at 3:37 PM, Adrien Monteleone
> wrote:
>
> Since John indicated there is not an effort to adhere to the current Gnome
> HIG, that statement should probably be removed. (as they don’t conform any
> longer)
>
>
> On Sep 15, 2018, at 9:55 AM, David T. wrote:
>
>
>
>> On Sep 15, 2018, at 5:29 AM, Frank H. Ellenberger
>> wrote:
>>
>> As we are already there,
>>
>> one of you Davids might also review
>> https://github.com/Gnucash/gnucash/blob/maint/README section overview,
>>
>> and probably files
And if we’re going there, the main project includes numerous README files in
gnucash/doc, all of which need similar treatment. README files for WIN32, HCBI
and OFX should IMHO be removed altogether in favor of other venues (didn’t HBCI
get replaced by FinTS in, like, 2002?).
David
> On Sep 15,
> On Sep 15, 2018, at 1:22 PM, John Ralls wrote:
>
>
>
>> Furthermore, in the interest of eliminating bit rot and in using the right
>> tool for the right job, I would strip the README back drastically to cover
>> only basic technical details on downloading, installing, and running
>> Gnu
Perhaps ‘double entry accounting’ would be more accurate than ‘financial
management’.
Regards,
Adrien
> On Sep 15, 2018, at 12:21 PM, David T. via gnucash-devel
> wrote:
>
> To be specific: in the main README, I would eliminate the Overview
> altogether, and replace it with:
>
> GnuCash is
David
Main reason I pushed it through to the current Help manual is that I had it
completed to slot in there already apart
from a bit of minor debugging. If the current vesion of the guide continues for
v3.3 I thought it was worth having it in
the help manual at least. I agree it is really mate
> On Sep 15, 2018, at 9:47 AM, Robert Fewell <14ubo...@gmail.com> wrote:
>
> Hi,
> Came across this today when trying to find a build with a working register
> date edit to see if I can find which commit broke it.
> For information in a register, click in the date field which removes the
> sele
David,
I am not sure what is the best way to work on the new documentation with
you. One way fo doing it would be for me to fork your personal repository
into mine. I can then add the changes into your bug branch, push them to my
PR and then create a pull request to your PR to pull the changes i
13 matches
Mail list logo
