Documentation translators: Changed para in ch_oview

Geert Janssens geert.gnucash at
Tue Aug 9 03:48:14 EDT 2016

On Tuesday 09 August 2016 09:46:00 David T. via gnucash-devel wrote:
> Frank,
> As a git-challenged documentation contributor (I imagine my
> git-clutziness is well-documented), is there a non-git way you could
> present your change, so that I might examine it and maybe comment?

Can you read a diff file or a patch file ? In that case you can look at the following webpage (on 

Note that due to the way the Italian translation is set up, this commit contains a huge list of 
changes to the Italian translation file (it.po). Unless you want to take on the Italian translation, 
you can skip all these changes.

Otherwise what would you suggest to make it easier on you ?

Note I don't expect you to understand git and send patches in git compatible format. The github 
website on the other hand i more than just a collector of git commits. It comes with several 
useful "reporting" features. One of them is it can visualize the changes in one single commit in a 
way that's IMO fairly readable without understanding git. I hope that part works for you as well. I 
would no doubt have been more useful to you if Frank provided you with a link to click on.

> To the list:
> Is the group hoping to move away from bugs on Bugzilla in favor of an
> all-git process? ISTM that recent comments on the lists hint at that
> direction. As I note above, this can act as a barrier to some of us
> technologically challenged individuals. Perhaps it is not such a big
> deal for code developers, but documentation involves a much different
> contributor base.

You're confusing git and github here, but that's ok. Short clarification: git is only a mechanism to 
store source changes in a way the history remains manageable. It's very powerful for that, 
which makes it challenging to learn to use efficiently.
In itself it lacks all kinds of other tools required for development, like a feature/bug tracker, wiki 
pages,... Github is one website that has set up all these things around git and much more. It's 
goal is to provide a more convenient way of working with git by providing a graphical interface, 
and some additional useful features wrt collaboration.

Having said all that there is no intention I know of to move to a purely github based process - 
particularly not for the documentation - even though some of it's features are very handy. You 
are still welcome to provide patches via bugzilla (we're not even using github's issue tracker, 
hah! ;) ).



More information about the gnucash-devel mailing list