--nextPart2357688.PtHLpp78yY
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Maurizio Monge wrote:
>Looks like that you (you all?) did not understand what Paolo was asking.
>Paolo stated *very clearly* that he was not asking a switch to git but
>just *some support* for projects that would like to use git and still
>being part of the KDE project.

No, I think we did.

The problem is that you're skipping the whole months of discussion on what=
=20
KDE's next VCS will be. Everyone asking for git right now is skipping=20
that.

>For instance being able to register a git repository on kde.org would
>be a very good step in this direction (consider also that git does not
>even require a "git" server, http or ssh will just do!).
>I really don't understand your accept_or_die policy, if a project
>would like to use a different VCS i think that no *very good reason*
>is required.
>Considering that KDE has the very liberal policy "you have write
>access for almost everything" (an i'm happy of it), i don't understand
>why you should impose "but you must use SVN!!!"

There are a couple of reasons:
1) setting up a repository is more than just "here's an ssh account". It=20
means the server where that ssh account is hosted must be secured so that=20
the ssh account won't be a vector for a hack attempt. It means the server=20
needs to have some shared space where other ssh accounts can read and=20
write to. It also means there must be a backup procedure in place.

All of that means more work to the sysadmins, who already don't have much=20
time.

2) we will not port our scripts to other VCS. That's scripty, that's Krazy=
=20
(EBN), that's the Coverity scan. That means you *still* need to import=20
code to subversion for translations and all those goodies.

3) if we allow git, we'll have to allow hg, darcs, bzr, etc. Then it's no=20
longer "one more tool" to learn, it's several.

4) many people build all of KDE and do fixing commits here and there as=20
needed. It depends on their goodwill to move to another system. Heck! I=20
know many developers who took over a YEAR to move to Subversion after we=20
decommissioned CVS! If we bring in several more repositories, those=20
people will probably not build your code and test it.

I think the most important points are 2 and 4. I believe that moving code=20
away from Subversion means it'll decrease in quality. And it'll have no=20
translations...

=2D-=20
=A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org
=A0 =A0 PGP/GPG: 0x6EF45358; fingerprint:
=A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358

--nextPart2357688.PtHLpp78yY
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBGlhNIM/XwBW70U1gRAkZMAKCFSBYq/Ko25160qha/hQlg5DkDYwCgixEk
cADv5PlQzOuOYfNH1Gq8yfs=
=CxSG
-----END PGP SIGNATURE-----

--nextPart2357688.PtHLpp78yY--