[Kde-scm-interest] svn, git, bzr

[Friedrich W. H. Kossebau]

Am Donnerstag, 24. Juli 2008, um 00:39 Uhr, schrieb Tim Penhey:
> On Wednesday 23 July 2008 21:53:28 Thomas Zander wrote:
> > To the question that inevitably comes up in these threads of what the
> > advantage is of one scm over the other I typically answer that git is the
> > one tool that actually does not dictate any workflow. Its flexible enough
> > to adjust to your workflow.
>
> I think that this is often a feature of any DVCS over a centralised one.
>
> I don't want to get into a DVCS argument here as this is not the time, nor
> the place.
>
> Personally I prefer Bazaar as it fits to how I work, and is equally
> flexible in workflow, some say more so, as git.

Has anybody yet thought of this answer:
a (freedesktop) specification for the protocol and the repository model! :)

So the model and api of a repository storage would be standardized and 
everyone could use locally and with her peers in the subproject what they 
like. Should be possible, the basic system of all the solutions (incl. Darcs 
and Monotone) seems so similar in the interface and should be mappable. But 
yes, not a target to develop and implement inside the KDE project, we want a 
product ready to use :)

And please, a new SCM system should be chosen by good matching of technical 
needs and other usual numbers, and not on the number of fanboys. If a system 
is really good, it should be also easily learnable, so switching for anyone 
is no point, thus many being used to one isn't, too.
(Most of us only know one of the hyped ones anyway. And some of the verbose of 
us remind me of a close family member which always tells me how better 
Windows is than Linux. And even freely admits he has never used Linux, just 
points to all the other experts who are talking about how better Windows is, 
too ;) Let's all please look out and listen to those who have really gathered 
longtime and deep experience with multipe product solutions.

But now my biggest wish:
There is no entry on techbase for this project if I searched sufficiently. So 
is there another collection of what has been done and thought already on 
this? It would be great to know why some are unsatisfied with the current 
system, what they want to have (in features, not product solutions!), what 
solutions they know of and where one could see how the solution proved to be 
working. Or link collections to interesting articles on the topic, like 
experience reports (like: From svn to $DVCS and back ;)
Mailing list archives suck for this purpose.
Should I create a subsite below http://techbase.kde.org/Projects? Which name?

I am especially interested how accountability (or what the term is) will be 
treated if some code is developed off the central repository system. With the 
current central system every commit is bound to one account, checked by 
password. But how to handle the merge of a branch in another repository with 
perhaps local accounts, not given by the KDE admins? How should copyright 
assignment be handled? BTW, doesn't the same problem already arise with 
subversion today when svnmerge is used, as done e.g. in the merging of the 
PIM enterprise branch, which are commited by one person and have no clear 
authorship (thus copyright ownership) registered with the system, IIUC. Is 
this alright?

Cheers
Friedrich
-- 
Okteta - KDE Hex Editor, coming to you with KDE 4.1