Gallery and Rosetta

Wed Nov 29 08:40:41 GMT 2006

El jue, 02-11-2006 a las 21:30 -0500, Chris Kelly escribió:
> On Oct 27, 2006, at 12:37 PM, Carlos Perelló Marín wrote:
> 
> > El jue, 26-10-2006 a las 19:54 -0400, Chris Kelly escribió:
> >
> >>   Some background: we use subversion
> >> on SourceForge to manage our code and there is a target in a Makefile
> >> that needs to be run to compile the .po files and make them usable in
> >> Gallery.  If I understood the FAQ correctly, Rosetta can stay in sync
> >> with a branch in SVN.
> >
> > Hmmm, no that's not true. What we do in Launchpad is to mirror CVS and
> > Subversion repositories as Bazaar branches. That's not related with
> > Rosetta directly. In the near future, we will implement a way to do an
> > automatic sync Bazaar <-> Rosetta from where we will fetch  
> > translations
> > from a Bazaar branch and will export updates as a new branch.
> 
> Ah ok. This makes sense.
> 
> >
> >>  Is there more information on how this works?
> >
> > Here: https://wiki.launchpad.canonical.com/RosettaTranslatesBranch,  
> > you
> > have the initial spec we wrote to implement this feature, it's not the
> > final one and, as I already said, it's not yet implemented.
> 
> It sure looks like an initial spec :) Hopefully I can provide some  
> good feedback for you from the perspective of someone not hosted on  
> Bazaar.

Cool

> 
> >
> >> How frequently is synchronization done? Would there be any way for
> >> our language makefile target to be run before Rosetta makes a
> >> commit?  When .po files are updated in SVN, could/does Rosetta grab
> >> them? How are conflicts handled?
> >
> > As we didn't started its implementation, would be quite useful if you
> > share with us the 'perfect' system from your point of view.
> >
> > Take care that we shouldn't have conflicts because Rosetta will never
> > touch any development branch, it will have its own branch that you  
> > will
> > need to merge from to get translations so you control/handle conflicts
> > and translations. The concept is that if you want that feature from
> > Rosetta, your translators will submit their translations using Rosetta
> > (they can use our web interface to translate or just download a .po
> > file, translate as usual and upload it again to publish it.
> 
> 
> Here's how the perfect system would work from my point of view:
> 
> 1.  We sign up Gallery with Rosetta and give it svn access to our  
> repository hosted by sourceforge (Rosetta would have a sf.net  
> username that we could grant write access to our project and notify  
> Rosetta once this was done)

I guess this would be to do commits from Rosetta... 

> 2. Rosetta would track our source code via svn, regular/nightly/etc  
> updates would be good, perhaps following a tracking system such as  
> the -checkins mailing list or CIA would be nice.

This is already done by our svn->bzr process daily.

> 3. Whenever a translator started work in Rosetta on Gallery, Rosetta  
> would ensure that the file they were working on was up to date.

Once we link Rosetta with bzr, we should be up to date (or at most, miss
only changes since last sync.

> 4. Whenever a translator finished their work and saved it, Rosetta  
> would make a commit directly to Gallery svn of only the updated  
> language files and would include a good log message (this would  
> require running a Makefile with our current setup)

I'm not completely sure whether the automatic imports should be done...
but it's doable. But...

> 
> This would allow minimal management overhead on our end, the  
> flexibility of translators to use svn on their own or Rosetta to do  
> translation, and the ability for changes to show up immediately.

There is a race condition here:

1. We check that we are up to date
2. Someone starts translating in Ubuntu.
3. You or any other translator updates the same .po file in SVN
4. We do the commit to SVN.
5. Conflicts!!

Most of the time, it will work, but that race condition is there, how
would you handle that?

> 
> Does that make sense and sound possible somewhere far down the line?  
> (Or are you primarily concerned with working with projects hosted on  
> Bazaar?)

At the moment, our primary target is to work with Bazaar trees. Anyway,
there is a work in progress plugin for Bazaar that will allow us to do
commits to SVN repositories from Bazaar branches (I'm not completely
convinced about this). The read of CVS/SVN repositories is already
solved with a mirroring tool that converts them in Bazaar branches.

Thanks for your input!

> 
> -Chris
-- 
Carlos Perelló Marín
Ubuntu => http://www.ubuntu.com
mailto:carlos.perello at canonical.com
http://carlos.pemas.net
Alicante - Spain
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente
Url : https://lists.ubuntu.com/archives/launchpad-users/attachments/20061129/19d1a9a3/attachment.pgp 