Re: [Discussion] Pootle Migration - Git Connection

2022-06-11 Thread Mechtilde

Hello at all,

the process which is already implemented is:

I wrote a shell script which export every night (2 am CET) the data from 
the database to have recent po files. Then I copy them into my home 
folder at the "pootle" server, where I commit it into a git repo.


Then I can get the po files to my own system to generate the sdf files.
this step was required as log as I had to use ubuntu 18.04.

There is no problem to give more persons access to the group of my home 
folder.


Kind regards

Mechtilde


Am 11.06.22 um 14:54 schrieb Arrigo Marchiori:

Hello All,

On Sun, May 29, 2022 at 11:41:09PM +0200, Peter Kovacs wrote:


Hello all,

I am still working myself into Pootle.

Pootle stores the translation at default on the filesystem. There is a
backend which can utilize git. Pootle commit changes on the translation
towards the git repository.

It would give us maybe the opportunity to maintain different Iteration of
OpenOffice Translation texts.


Storing any development effort into a version control system is IMHO a
good idea.

I think that the best way to do it, would be the easiest, technically
speaking.

For example: if you want to configure Pootle to use Git, you will have
to let it authenticate in some ways. If it's easy, then go ahead!

The alternative would be having someone manually pushing changes from
the filesystem into the repository. This could be done on a periodic
basis; say every two weeks.

To summarize: +1 for Git, in whatever way it is easiest to configure
and to maintain.


For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could
use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation
files.


I agree that branches would be most useful.


We could then think of a Version Mapping and a back push translation system.
This is just a crazy Idea at this moment, to manage the string changes
between Versions.


What do you mean exactly?

I would expect l10n-savy developers to push changes from the Pootle
development repository into AOO41X or other branches, at appropriate
times (for example, before a beta release).


What do you think? Is this an Idea to look into? Please write me your
opinion. Thanks.


I hope this helps.

Best regards,


--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows und OS/2
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: [Discussion] Pootle Migration - Git Connection

2022-06-11 Thread Arrigo Marchiori
Hello All,

On Sun, May 29, 2022 at 11:41:09PM +0200, Peter Kovacs wrote:

> Hello all,
> 
> I am still working myself into Pootle.
> 
> Pootle stores the translation at default on the filesystem. There is a
> backend which can utilize git. Pootle commit changes on the translation
> towards the git repository.
> 
> It would give us maybe the opportunity to maintain different Iteration of
> OpenOffice Translation texts.

Storing any development effort into a version control system is IMHO a
good idea.

I think that the best way to do it, would be the easiest, technically
speaking.

For example: if you want to configure Pootle to use Git, you will have
to let it authenticate in some ways. If it's easy, then go ahead!

The alternative would be having someone manually pushing changes from
the filesystem into the repository. This could be done on a periodic
basis; say every two weeks.

To summarize: +1 for Git, in whatever way it is easiest to configure
and to maintain.

> For example. 4.1.x and 4.2.x Translation sets do not match. Maybe we could
> use Git to have a 4.2.x branch,another branch will contain 4.1.x Translation
> files.

I agree that branches would be most useful.

> We could then think of a Version Mapping and a back push translation system.
> This is just a crazy Idea at this moment, to manage the string changes
> between Versions.

What do you mean exactly?

I would expect l10n-savy developers to push changes from the Pootle
development repository into AOO41X or other branches, at appropriate
times (for example, before a beta release).

> What do you think? Is this an Idea to look into? Please write me your
> opinion. Thanks.

I hope this helps.

Best regards,
-- 
Arrigo

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org