Git Migration Needs YOU!
hein at kde.org
Tue Mar 2 10:29:24 GMT 2010
On 03/02/2010 11:05 AM, Till Adam wrote:
> 4) Handling of translations is a big worry, we currently don't really have a
> clear idea of how translations are to be handled with git at all. Has this
> been discussed yet? If so, is the result documented? It seems Amarok has
> somehow solved this for KDE 4.x, but we still actively work on at least the
> German translations for KDE 3.5. Porting the e35 translations infrastructure
> to the KDE4 one would be a considerable undertaking, requiring a specialist
> (hey, David :).
The translations for Konversation (to use this opportunity:
we could use some help porting our KAddressBook integration
to Akonadi) and Amarok are still in SVN. Nothing has changed
for the translators at all, in fact - scripty abstracts the
difference away by grabbing from and committing to our git
There are currently no plans to move translations into git.
> Thiago mentioned that kdepimlibs is a new module, and thus does not need any
> work, but that's not true, as all of that code has a long running and valuable
> history all the way back to the cvs days. Which was, so far, retained.
Yeah, tracking moves like that, as well as things like apps
moving from playground into kdereview and then finally a mo-
dule, is why Thiago's old ruleset if woefully incomplete and
why writing the rules files is such a mammoth task (and will
need the cooperation and collaboration from actual develop-
ers on the respective codebases to make certain decisions
at times, etc.)
More information about the kde-core-devel