[Qgis-community-team] Transifex and doc 1.8

[Alexander Bruy]

Hi,

I agreed with Nathan: it is better to stick with usual git workflow
and avoid any type or redundancy as much as possible.

When we used SVN for docs we have same workflow — separate branches
for each version and I can't remember any problems with this from
translators side.

Moreover putting sources to Transifex is single operation and
performed only when new version of the docs is out (BTW, I still
prefer to use git and offline translation).

Just my 2 c.

On Mon, 01 Apr 2013 21:27:12 +0200
Richard Duivenvoorde <richard at duif.net> wrote:

> Hi Nathan,
> 
> no I'm not talking about a different repo, but  a copy of a directory in 
> the same (documentation) repo in master (after a release).
> 
> So now we have:
> https://github.com/qgis/QGIS-Documentation/tree/master/source/docs
> 
> and I my idea was to have IN the user_manual directory, a version of the 
> user_manual for every version
> 
> source/docs/user_manual/master (dev version)
> source/docs/user_manual/1.8
> source/docs/user_manual/2.0 (a copy dev version after 2.0 release) etc
> source/docs/qgis_governance is ok (no need for a new version)
> but
> source/docs/pyqgis_developer_cookbook/master
> source/docs/pyqgis_developer_cookbook/1.8
> source/docs/pyqgis_developer_cookbook/2.0
> etc
> 
> I know it is redundancy, and from a coder/github point of view this 
> should be done via branching and or tagging, but for a non-coder pov I 
> think it is more clear and 'transparant'.
> 
> But (even more important) we could just put the full source directory 
> into Transifex, no need to think about which version is to be put in 
> there etc etc..
> Making it easier to just fix an error in whatever translation you find 
> important.
> 
> For the git-users it is still possible to use github (only without 
> branches, allways working in 'master')

-- 
Alexander Bruy