< Projects
Revision as of 22:27, 11 November 2009 by Argonel (Talk | contribs)

Jump to: navigation, search

This is the page for co-ordinating KDE's move to git.

If you're interested in helping, you should join the mailinglist and #kde-git on freenode.


The Plan

KDE is, eventually, moving to Git. We will be using servers, with funding from Nokia. We will also have our own mirrors using existing KDE servers.

We are working with the Gitorious people to ensure their server will meet all our needs as well as everyone's privacy requirements. The distributed nature of Git will make it easy for us to migrate off at any time should the need arise (but that's unlikely :).

In the summer of 2009, Amarok moved to Gitorious to test the waters and find problems that would affect KDE. Once those problems have been solved, all of KDE will be able to switch.


Git offers many advantages over svn. [TODO: examples] Many KDE developers are already using git-svn, but this tool has its limitations. We want to have the full power of Git available, and we have people willing to do the work necessary to migrate.


When we move, KDE's svn repository will be migrated into several Git repos, all on main modules such as kdelibs and kdebase will each become one repository. projects in extragear will each have their own repository. The site will have a list (lists?) of all these repositories. Scripts will be provided for downloading, say, all of extragear.

A few things will stay in subversion - currently websites, translations and manuals. It's possible they could move to Git later, but they won't be part of the mass migration.

On Gitorious, all KDE developers will be part of the kde-developers group. Developers in this group are required to set their "full name" for their Gitorious account to their real name. If you are not in this group or do not have an account, a system will be set up to simplify the process. Or you can just go to Gitorious yourself, create an account, and ask to be added to the group. :)


Modules like kde-edu might not want to be a single repo; that remains to be decided. Playground will probably become obsolete, since anyone can make their own little repo. But then how do I find all of the playground plasmoids?


Tasks that need to get done before we can migrate

e-mail notifications

0% completed (estimate)


Owner: Gitorious

Everyone added to the kde-developers group gets an e-mail when anyone makes a merge request to any of our projects. This is undesirable (as most kde devs are not Amarok devs and many other permutations). A solution for this will have to be developed on gitorious before all of kde goes to gitorious.
johan will be working on this at the next gitorious sprint.


At a minimum, users need the ability to choose which projects to get email from. It would be really awesome to have more fine-grained control, though, like the commitfilter. konqueror and kwin and plasma will all be in the same git repo but I only want merge requests for one of them. --Chani

Method for joining the team

0% completed (estimate)


Owner: (unknown)

The svn account-creation process needs to be upgraded to include creating a gitorious account (if none exists) and adding it to hte kde-developers group.


drf suggested a git repo to do this, but the sysadmins may be happier with their bugzilla form. someone needs to contact them...

Account setup on Gitorious

0% completed (estimate)


Owner: eean, johan, boud, dario

Creating an account on gitorious isn't hard, but asking to be added to the kde group is inconvenient. For the migration we should set up a system (via email or wiki?) where developers can ask to have an account autocreated for them, or add their existing gitorious account to a list to be added to the group. Once this is in place an announcement should be sent to all svn accounts explaining the process, and privacy information.

We also need to ensure everyone in the kde-developers group is on the kde-cvs-announce list, and... our sysadmins need admin access to gitorious? to create the accounts, I guess?

Discussion I'm not sure what gitorious access sysadmin needs... need to check on that...


50% completed (estimate)


Owner: Ian Monroe, Gitorious

Commit filter is not implemented on gitorious (or something similar) though rss feeds for each module you are interested in can be subscribed to in the meantime.


The technique I used to do it wouldn't really scale to the rest of KDE (though it could in a pinch). Would rather have a gitorious-enabled solution. --eean 18:18, 11 November 2009 (UTC)

pre-commit hooks

0% completed (estimate)


Owner: (unknown)

acltest, docbook, EOL/UTF-8
A web hook isn't good enough for these because they have to run and return whether to allow the push, for every single push to every kde repo.


gitorious guys said they *might* be willing to allow a few scripts on their server for kde as a special exception, iirc. --chani
Yes, at least for basic things, heavier things like doc building would probably have to be mirrored (goes for pre/post) --johan-s
It turns out that acl and docbook might not be needed so long as web and docs/ stuff stays in svn.

post-commit hooks

25% completed (estimate)


Owner: (unknown)

  • email/CIA
  • license header checks
Gitorious is supposed to provide web hooks for this; have they started? who volunteered to write the scripts once that's done?


There is a branch of gitorious called web-hooks --Panagiotis Papadopoulos 1 November 2009
Same situation as commit emails --eean

Get rid of svn:externals

0% completed (estimate)


Owner: David Faure

not possible with git, broken by design.


Is there a list of instances of svn::externals anywhere?- -Yokem55 19:27, 1 November 2009 (UTC)

Snapshot to read-only svn

0% completed (estimate)


Owner: Simon

It's work, but maybe some people would like it. NEEDED for documentation, in order to get it back into SVN for the translators/scripty/?


Could be done with a git-svn gateway presumably? -Mike Arthur 19/10/2009 16:04

Techbase Documentation

Owner: Chani, greeneg, - please help out!

10% completed (estimate)


At least minimal documentation about how to checkout, how to get a gitorious account, how to request a merge needed, other git documentation and links to other git information would be very useful also.


Nice to have before the migration:

Talk to people using other distros about git

0% completed (estimate)


Owner: Sebas


Talk to windows guys about git.

0% completed (estimate)


Owner: Danimo



100% completed (estimate)


Owner: darktears

This should be easily done with gitorious web interface and merge requests actually.


but reviewboard has features gitorious (right now) doesn't, like commenting on specific lines and not having to set up a merge request. --chani
Also email notifications when someone reviews are needed --thomasz
We're working on this for someone else right now, so pretty soon --johan-s
I consider the latest changes to gitorious to finish this. If more reviewboard features are still needed, and git supports reviewboard, I think this is something we can look at doing post-conversion. --Ian Monroe

Opt-in privacy exception required for kde-developers

0% completed (estimate)


Owner: Gitorious

We need a mechanism (possibly as simple as a new field on kde-common/accounts) that will let us do stuff like email all account holders. This is important for major announcements, and for invalidating dead accounts.
It would also be good to have direct backup access to the SQL database, so that we could setup our own in case it goes evil or something. This would also likely require a privacy exception, to allow Gitorious to share that with our sysadmins.

SSH blocked in corporations and universities.

100% completed (estimate)


Owner: Unknown

Some universities tend to block the SSH port. There should be a workaround to use SSH on some different port. already runs a SSH server on port 443. But that assumes you are using a proxy. It has been found that this hasn't worked with a lot of people, especially those who have a direct connection to the internet ( so some transparent blocking by the ISP ). It would be great if (almost) every KDE developer were to be asked to check if other ports work before KDE made the switch. Otherwise there could be an automated email where the git patches could be sent, and appropriately patched to the right location too.

Discussion, and there's always been HTTP cloning (although the current impl. in Git is a bit on the slow side) --johan-s

Post-migration stuff:

Website Branding

2% (initial ideas on the table)


Owner: ruphy

KDE gitorious should be branded accordingly, and should be reachable from as well as


other notes

convert all accounts to SSH?? multiple git repos joined?? - use repo tool from android?

KDE accounts file is no longer necessary---used for mapping svn ID -> email, but we have that now from gitorious. might be a good guide on what docs we need.

some of this stuff was from the list from GCDS that was in this email


TODO merge this with the todolists above

michael jansen: talking to kdesvn-build/mpyne
--Done? -> -- Panagiotis Papadopoulos 1 November 2009

  • Yes, but the __kdesvn-build-remote used in the impl isn't pleasant for users already on git so it still needs more work for them. Mpyne 20:32, 11 November 2009 (UTC)

thiago and sebas: funding

jonas: domain name

thiago: actually convert :D (ThomasZ put some work in the converter tool to make it easier to use; see his 'svn2git' project on

ML: convert to SSH

chani: techbase docs for scripty

thiago: pre/post-commit hooks

sebas/lydia/leo: communication with teams! tell people! keeping track that everything is being done.

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal