[Localization] New localisation workflow: Overview and status

[Sayamindu Dasgupta]

Hi,

On Thu, 2007-11-01 at 11:09 +0100, Marco Pesenti Gritti wrote:
> On 11/1/07, Rafael Enrique Ortiz Guerrero <dirakx at gmail.com> wrote:
> >
> >
> > On 10/31/07, Marco Pesenti Gritti <mpgritti at gmail.com> wrote:
> > > On 10/31/07, Sayamindu Dasgupta <sayamindu at gmail.com> wrote:
> > > > ** Current Status **
> > > >
> > > > Most of the scripts, etc are ready, and we are quite satisfied with the
> > > > results of what we have seen so far using local repositories. The only
> > > > major "blocker" issue that is left to be resolved is the question of GIT
> > > > access to dev.laptop.org for the Pootle user. The most optimal solution
> > > > for this is to use the newly released support for GIT submodules (where
> > > > the po directory can be a separate submodule of a project). This
> > > > isolates the PO directory from the rest of the project, minimising the
> > > > chances of Pootle messing something other than translations :-).
> > > >
> > > > However, we would like to hear from developers on this - does having a
> > > > new submodule under your project tree complicate your job ? Information
> > > > on git submodules and how to use them is available at
> > > > http://git.or.cz/gitwiki/GitSubmoduleTutorial
> >
> > From my point of view this is not really necessary, we can keep on doing our
> > actual simlinks and script scheme, although is not an entirely integration
> > to git (from the pootle point of view), from the d.l.o side is the  better
> > solution, but anyway  im not saying that we shouldn't keep on trying to find
> > a complete solution for this, but this solution  does not have to be so
> > complex.
> >
> > So i agree with marco that we have to write a tutorial about this, but the
> > procedure is not difficult, taking in count that we have to handle the
> > translation sync from the translate machine, and this is made by git pull
> > from all the activities.
> 
> Yeah, my request for a "tutorial" was about the submodule part. It
> felt too complex at first sight but I wanted to see exactly what we
> was going to require for activity authors.
> 
> Anyway if we can avoid the step altogether I'll be happy :)


It will actually add an extra level of complication for the software
developers. 
To add a GIT submodule, one would have to do a git submodule add <repo>
inside the existing main repo. However, it will probably cause confusion
since the submodules are not checked out automatically and one has to
pull them in explicitly.

The only reason we wanted submodules was to ensure that Pootle had write
access to _only_ the translations, and nothing else - but I guess it
adds too much complexity for the developers (and on top of that,
migrating existing projects to a submodule based setup might be a major
pain in the backside :-). I had a small discussion with Xavi on IRC
about this, and he thinks likewise on the complexity issue.

I would love to hear some comments from someone from the server admin
team on this. 

Warm regards,
Have a great day,
Sayamindu

 
-- 
Sayamindu Dasgupta
http://sayamindu.randomink.org/ramblings