[Kde-scm-interest] Some ideas

[Albert Astals Cid]

A Diumenge, 7 de juny de 2009, Lorenzo Villani va escriure:
> ===== How to deal with "the push bit":
> Being a collection of individual projects only the 'core' developers are
> given initial push access to a project's repository, they can then add more
> people as they see fit. I know that KDE developers are not used to this
> (everyone has commit access to each other's code) but I think that this
> should improve overall code quality as new contributors are first required
> to submit their code for review before inclusion.

You _think_ that core developers having access is good, our experience shows 
that everyone having commit access is good.

> However, if project's core developers want, they can open their project to
> all kde developers. (Technical details are expressed in the
> "Infrastructure" section).
>
> ===== How to handle the migration
> My proposal is to track history inside git only from KDE 4 onward and keep
> earlier history in compressed tarballs of the subversion tree and make them
> available somewhere.

No, all history is needed.

> == Scripty
> My proposal is to replace scripty with another translation system which
> supports git by default.
> However I have no direct experiences with any of the tools around.

Good one, say that our working tool needs to be replaced and then say you have 
no idea of what you are talking about

> There's Rosetta, but that's Canonical's stuff and AFAIK it's tied to
> Launchpad and bzr.

Rosetta is not free software afair and even if it was forget about web based 
systems, we that work and know the translation workflow don't like them.

Albert