Hi Pedro.
Am 03.01.2026 um 18:05 schrieb Pedro Lino via dev:
Good Year to all!
On 01/02/2026 2:26 PM WET [email protected] wrote:
This is open for discussion, and I thought this are the topics we should
try to tackle this year. What is your opinion?
Apache OpenOffice:
- 4.2
-- Get an actual translation import
-- fix remaining blockers
In my opinion if we can get a translation server working, import current
translations, get contributors to complete them and can include these
translations in a working 4.2 build, I would be very happy.
Thanks, for this reminder. How about following Phases:
Phase 1: one extract for new dev build pootle files to sdf
Phase 2: manual trigger translation sdf to pootle files
Phase 3: Automate build bot sdf extract to translation GitHub repo
--- 2027 --- (I just think there are so many topics i am currently
involved that this is more realistic, but if there are supporters that
help to work along the roadmap we could be faster.)
Phase 4: automate translation -> translation GitHub
Phase 5: automate translation sdf export to GitHub code repo as pr
Phase 6: Automate triggered build for translation PR
in parallel Move to Weblate. I am not sure how fast i have a version ready.
in parallel move pootle to new translation server (this is a parallel
request from infra, to decommission the current translation server. And
we move to a docker image based setup. I currently hope that i maybe can
save some work by setting up the weblate directly.
but i am working kind of on both. )
Releasing a public 4.2 build in 2026 would be fantastic!
Yes, i want to push that. We talk way to long for this step.
Best,
Pedro
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
