[Kde-scm-interest] Git roadmap

[Mickael Marchand]

Hi,

just some random thoughts,

On Mon, Sep 17, 2007 at 09:13:32PM +0200, Thiago Macieira wrote:
> In order for KDE to switch to git, I think we need to address three major 
> areas:
> 
> 1) git support for all features we want/need
>   We need to identify which features we want/need in git that aren't 
> present yet. We also need to make sure that git's features works as 
> expected by KDE developers.
>   I already have two things to add here.
> 
> 2) the conversion from Subversion to git
>   Chris's work on the git-svn-fastexport tool is a good start, but our 
> repository is extremely complex. We need to develop the tool further to 
> be able to import the repository correctly.
>   Someone on #git has suggested we import all of SVN into one monstruous 
> git repository and then work from there, inside git. I believe, however, 
> we can extract some more metadata from Subversion (read: file-copy 
> relationships)
> 
> 3) repository layout, ACLs, hooks, etc.
>   First and foremost, switching to git brings the question of whether we 
> should have multiple repositories in KDE (as opposed to a single one like 
> we have with Subversion). I'm not talking about clones. If we have 
> multiple repositories -- which is the recommended way in git -- we have 
> to decide where to split and how to glue everything to gether with 
> submodule support.

I believe if we split, this is something almost irreversible if at some
time in future we want to move to <insert some fantastic centralised
SCM> here. Migrating one single centralised repository is already a
pretty big deal, migrating multiple repositories into one would even be
harder (keeping history I mean), so this is a big decision that needs
carefull attention imho.

> 
>   Then we need to think about the "social" side: who gets push access? Who 
> gets fast-forward-only push access? Will we require "SignedOff by"? Where 
> will we keep our post-commit hooks, like the kde-commits at kde.org mailer? 
> How will we protect the official tags? How will we protect the Root CA 
> files in kdelibs? Etc.

hmm my git knowledge is still poor, do you mind explaining the
difference between push/fast-forward-only ?

having post-commits is something easy in git I think, kde-commits can be
revived easily I think. (we could also have separated
kde-commits-submodule lists for each git repository also)

does git have any sort of ACL stuff like subversion has ?
I have not seen that yet, but haven't really looked for them.
it seems there is a pre-commit hook, I guess we can do all filtering
from there just like subversion ?

Cheers,
Mik

> 
> In this thread, I'm not looking for the actual issues. We'll have separate 
> threads for that. This just food for thought. Do people have more things 
> to add to the plan?
> 
> -- 
>   Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
>     PGP/GPG: 0x6EF45358; fingerprint:
>     E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358



> _______________________________________________
> Kde-scm-interest mailing list
> Kde-scm-interest at kde.org
> https://mail.kde.org/mailman/listinfo/kde-scm-interest