From kde-scm-interest Tue May 08 16:18:14 2012 From: Vishesh Yadav Date: Tue, 08 May 2012 16:18:14 +0000 To: kde-scm-interest Subject: Re: [Kde-scm-interest] Migration of KDESDK to git, finally? :) Message-Id: <4FA94476.5030700 () gmail ! com> X-MARC-Message: https://marc.info/?l=kde-scm-interest&m=133663376406385 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0080803483861844688==" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============0080803483861844688== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBBD1F7F3990B8CFDBB7EED0E" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBBD1F7F3990B8CFDBB7EED0E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable As far as plug-ins are concerned, I think it would be better to have one repo per group. I don't see much benefit of having separate repository for each plug-in. Thing about plug-ins is that there can be many of them, and it would result into many repositories if go for other option. Regards, Vishesh On 05/08/2012 08:41 PM, Friedrich W. H. Kossebau wrote: > Hi, >=20 > KDESDK currently is still in svn. At least for Okteta I would like to h= ave > a move from svn to git as soon as possible. >=20 > While there have been two threads about this on this list, > "migration of kdesdk to git - status?" from 18.12.2010 and > "Idea: Converting KDESDK incrementally" from 28.03.2011, so far > nothing has happened, besides Kate and kdesrc-build having moved out > of KDESDK to other modules. I would like to change that and have someth= ing > happening :) >=20 > The gist from the threads is that > * the KDESDK module should be split into separate repos, as the single > submodules do not have anything in common, like libs or stuff > * the whole of KDESDK should be moved to git in one step, to reduce the= mess > for release managers, packagers and friends > Anyone disagrees? >=20 > Some brave people seem to have prepared set of rules for all the compon= ents > of the KDESDK module (thanks to them), see > https://projects.kde.org/projects/playground/sdk/kde- > ruleset/repository/revisions/master/show/kdesdk > What is the state of these rules? Can the result be checked somewhere? > Niko Sams, in the thread "migration of kdesdk to git - status?" as refe= renced > above you also talked about having prepared rules, are they in some way= > integrated in what is in the repo linked above? >=20 > Who are the current maintainers of all the submodules in KDESDK? I trie= d to > put all in cc: which looked like the one, see also below who I listed > for each submodule. >=20 > Looking through KDESDK I wonder what should end up in a separate git re= po > and what not.=20 >=20 > Standalone programs: > * cervisia - Christian Loose > * kcachegrind - Josef Weidendorfer > * kompare - Kevin Kofler > * lokalize - Nick Shaforostoff > * okteta - myself :) > * umbrello - umbrello devs > Surely one repo per program, right? >=20 >=20 > Plugins, grouped by type: > * dolphin-plugins > svn -Peter Penz > hg - Vishesh Yadav > git - Sebastian Doerner > bazaar - Jonathan Riddell > * kioslave > perldoc - Michael Pyne? > svn - Mickael Marchand? > * strigi-analyzer > diff - Laurent Montel/Jakub Stachowski > po - Montel Laurent/Nick Shaforostoff/Jos van den Oever > ts - Montel Laurent/Jakub Stachowski > xlf - Albert Astals Cid > One repo per plugin? One repo per type? >=20 >=20 > Development utils for KDE developers: > * kapptemplate - Anne-Marie Mahfouf > * kdeaccounts-plugin - Carsten Pfeiffer? > * kdepalettes - ? (and still useful? nothing build/installed here)=09 > * kmtrace - seems unmaintained > * kpartloader - David Faure > * kprofilemethod - David Faure > * kstartperf - Geert Jansen > * kuiviewer - Benjamin C. Meyer > * poxml - uh, no license headers! (Albert Astals Cid) > * scripts - lots of kde devs > Lots of small tools/helpers, basically not useful for anyone outside > KDE development. Dump in one repo? >=20 > I also wonder if these utilities here should not be split out into a se= parate > module, or the other way round, if all the "real" programs and plugins > should not make up a new module called "devtools"/"kdedev" or whatever,= > so the module with the "real" products can be better promoted to users > outside of the group of KDE developers. > And kapptemplate could also move to the module kdeexamples perhaps, as = kind > of code-to-copy/start-from? >=20 >=20 > Completely excluded from build are: > * kspy - Richard Moore > * kunittest - Jeroen Wijnhout > * scheck - Maksim Orlovich/Ryan Cumming > These should be moved to tags/unmaintained in svn in any case? >=20 >=20 > And while I have the attention of lots of KDESDK developers, would you = mind > if I take over the role as coordinator of KDESDK from Matt (in case his= offer > is still up) and mess^Wtry to clean-up the module a little? >=20 > Cheers > Friedrich --------------enigBBD1F7F3990B8CFDBB7EED0E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAEBAgAGBQJPqUR2AAoJEB/2Ajqoqz6pN3QH/j8D6tvaIuKY/KtJ2zAyp6fz KrXG1lDUyQvxCiXjyVB65cEGmhSse93xxJYQhCbrfEpIR5hBozMlnqt849rYTRX+ +C+iNDU6ZhEu+sHYPlKejD7AUsOi61n2DMcpBMRjDukIc7hmv/mAgvuqEdbGer58 xPcLbdSNAbSse2aX8/aBGPIIiw7V39VGSPbUbKvccRdpHZA0GmtsPGRgt1BOvNwu GdfEeHxfyWv25JosqBkdvLbVL5zS8/r7gPrGedPKD339EEP5O/2k0eNE4KUZMiKJ aN2s+6YYQVs43TnQFjPuAaw0nanIN9rsLLxxEdfbTSyNLYJnP6XDaZ1aLvv84Ss= =QeI5 -----END PGP SIGNATURE----- --------------enigBBD1F7F3990B8CFDBB7EED0E-- --===============0080803483861844688== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Kde-scm-interest mailing list Kde-scm-interest@kde.org https://mail.kde.org/mailman/listinfo/kde-scm-interest --===============0080803483861844688==--