[Kde-scm-interest] Process of moving a project from svn to git

[Eike Hein]

On 03/01/2010 10:42 PM, Andreas Pakulat wrote:
> What did I forget about?

I haven't had time to read the other replies in the thread,
but here's all the info you should need - read those two
log snippets carefully, and also the links toward the end
of the second snippet. In the end you should have the com-
plete checklist as well as detailled info about how the
repos needs to be set up:


[22:09] <Sho_> jpwhiting: Dunno. I could just wing it "we decided on the
last meeting" style. Other than that, what goes into moving is: (a)
Writing rules, (b) Converting, (c) setting up project and repo, (d)
pushing up, (e) straightening out the various group permission bits on
Gitorious, (f) Pointing scripty at the new place, (g) Cleaning up in
SVN, (h) Pointing EBN at the new place, (i) Pointing LXR at the new
place, (j) Changing the developer information for the app on the new
[22:09] <Sho_> www.kde.org (SCM and EBN links)
[22:10] <jpwhiting> wow, what you just typed (or more likely pasted) is
exactly what morice-net was looking for earlier
[22:11] <Sho_> jpwhiting: I didn't paste anything, that was lovingly
hand-typed
[22:11] <jpwhiting> cool cool
[22:12] <jpwhiting> Sho_: ok, you rock then
[22:12] <jpwhiting> want to send that via e-mail to morice-net, he
wanted that for something, not sure what

and

[22:13] <Sho_> KOffice is moving on March 4th
[22:14] <Sho_> Which I have zero information about otherwise, I'm sure
straightening out their repo permission bits will be fun
[22:14] <jpwhiting> hmm, cool
[22:14] <Sho_> (i.e. setting things up exactly as they're set up with
Konvi and Amarok atm)
[22:14] <jpwhiting> wonder why that date, but meh
[22:14] <jpwhiting> yep
[22:15] <jpwhiting> why would setting up the repo be any different than
konvi and amarok were?
[22:15] <jpwhiting> just add +kde-developers, right?
[22:15] <Sho_> No, not quite that easy
[22:16] <Sho_> Right now you have to have kde-developers, kde-sysadmin
and a <app>-reviewers group plus you need to add individuals who have
admin bits for the repository, or create another <app>-maintainers
[22:16] <jpwhiting> ah
[22:16] <Sho_> wait, I'll screencap the collaborators view for Konvi's repos
[22:17] <Sho_> jpwhiting: http://imagebin.org/index.php?mode=image&id=84270
[22:19] <jpwhiting> that's not too tricky
[22:19] <Sho_> jpwhiting: So you have kde-developers for commit rights,
kde-sysadmin for repo admin, some individuals for repo admin (so the
project can toggle force pushing to create tags or branches without
bothering sysadmin), and <app>-reviewers for merge requests and merge
request mail. And <app>-reviewers of course itself has both group admins
and regular group members (in Konvi's case, konversation-reviewers is
admin'ed by me and psn, the same people who also have admin
[22:19] <Sho_> privs on the repo).
[22:19] <jpwhiting> hehe, gitorious doesn't know who added kde-developers
[22:19] <jpwhiting> yep
[22:19] <Sho_> jpwhiting: Amarok is set up the same way, except their
reviewers group is called "amarok-developers" because it was originally
set up for a different purpose and then got reused for this
[22:20] <jpwhiting> yep
[22:20] <jpwhiting> Sho_: or better than mailing that list to morice-net
could you put it on techbase and link to it from MoveToGit? =)
[22:21] <Sho_> jpwhiting: Gitorious doesn't know who added
kde-developers because when I created the project and repos I created it
as owned by kde-developers so that was there since inception
[22:21] <jpwhiting> yep, that's what I figured
[22:21] <Sho_> jpwhiting: It's not tricky to set up for KOffice, no, but
I'll bet you a marzipan bar that it won't be set up that way right away
since I haven't seen anyone from KOffice participate here.
[22:21] <jpwhiting> TZander was for a while
[22:21] <jpwhiting> and boud
[22:22] <jpwhiting> but yes, you're likely right
[22:23] <Sho_> jpwhiting: Actually if you want to really grok the whole
thing, read
http://mail.kde.org/pipermail/konversation-devel/2009-December/003186.html
and then
http://mail.kde.org/pipermail/konversation-devel/2009-December/003195.html
and then
http://mail.kde.org/pipermail/konversation-devel/2010-January/003264.html
[22:23] <Sho_> jpwhiting: That's the explanations I wrote to keep the
Konvi people in the loop
[22:24] <Sho_> The second link also contains a short explanation of the
Gitorious permission model in general


I also attached the image linked to imagebin up there,
just in case.


> Andreas


-- 
Best regards,
Eike Hein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: collabs.png
Type: image/png
Size: 15671 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20100302/f14b72e7/attachment-0001.png