[Kde-scm-interest] Forming repos by plugin type or code domain? (was: Re: KDESDK->git: joining submodules in a singlerepo?)
Friedrich W. H. Kossebau
kossebau at kde.org
Sun Jun 3 17:29:42 UTC 2012
Hi,
so if everyone so far agrees that bundling by domain is the way to form the
repos, how would you like the layout, name and description of the repos?
I could imagine that the currently planned "lokalize" and "kompare" repos
simply integrate the plugins as additional features, but keep the old planned
names/descriptions. But you might have different ideas, so please tell.
Am Samstag, 2. Juni 2012, 12:44:24 schrieb Friedrich W. H. Kossebau:
> Hi Nick,
>
> Am Samstag, 2. Juni 2012, 12:54:16 schrieb Nick Shaforostoff:
> > is it possible to have po, ts and xliff strigi analyzers in lokalize git
> > repo?
>
> Sure it is possible. It's thankfully more a question if we/you want it to
> have them there :)
>
> And I guess there are also good reasons why there should be just one repo
> with all things related to translation (catalogs), which are:
> * Lokalize
> * the strigi analyzers for the catalogs
> * the thumbnailer plugin for po (new in kdesdk/thumbnailers/po)
Currently:
repo name / display name: lokalize / Lokalize
description: Computer-aided i18n translation
project manager (user id on projects.kde.org needed): ?, ?, ...
layout in kdesdk:
/
+- lokalize
+- strigi-analyzer
+- po
+- ts
+- xliff
+- thumbnailers
+- po
layout in repo?
> Even if that leaves just one analyzer in the "normal" strigi-analyzers repo,
> the one for "diff" files. Perhaps that could be moved to the Kompare repo,
> so bundling the code about diffing?
Same here. Currently:
repo name / display name: kompare / Kompare
description: Graphical File Differences Tool
project manager (user id on projects.kde.org needed): kkofler
layout in kdesdk:
/
+- kompare
+- strigi-analyzer
+- diff
layout in repo?
Cheers
Friedrich
More information about the kde-sdk-devel
mailing list