Sysadmin/GitInfrastructureLaunch
This document describes the time planning for the launch of the git infrastructure. Please note that this is the sysadmin time schedule. This will not contain the schedule for migrating the main kde modules, as that can only be done after the infrastructure is done.
The dates mentioned are our current planning, so if there is a set back along the way, we will adjust the schedule, be sure to check it every now and then. Announcements will be done on kde-core-devel and kde-cvs-announce on key moments.
Contents |
August 11th
By this time the svn repository is also accessible by ssh on port 443. This is an important moment, so every developer who currently has password access to the svn repository can move to an ssh based account.
This is also the moment that we sent out the last invitation for developers to move to ssh based accounts for the accounts not yet converted.
Completed: August 11th.
August 25th
At this moment the svn repository will be closed for passwd based accounts. Developers who have not yet converted have no access, but can still request conversion.
Completed: August 25th
September 1st
People who still have https based accounts can set their ssh keys in the gosa system at identity.kde.org. Changes made to kde-common/accounts file will be copied over by sysadmins to the gosa system manually, please file a sysadmin br.
From this time on every existing svn account holders can login into gosa and change their details. They can get access to gosa by using the password lost functionality. SSH key changes in gosa can be made but will be ignored for now. Non-existing account holders will not have access to gosa for now.
New account applications will be processed normally, but to keep the sysadmins workload a bit sane, we ask to wait for 2 weeks.
Completed: September 2nd
September 8th
Gosa will now be leading for the ssh keys. The keys listed there will be the ones that will be used to get access to the git repository and to the svn repository. Also the kde-common/accounts file will be automatically generated from the gosa data.
The syncing of that accounts file and the keys for svn access will be a manual task for now, so there will be a bit of delay. Changing the ssh keys will effect access to the git repository immediately.
Completed: september 4th
September 15th
From this moment on, we will launch reviewboard and redmine. Access to both services will be based on the gosa login data. The reviewboard will be a new (clean) instance, as the existing (old) reviewboard usernames clash with the new system.
Reviewboard: Completed: september 20th
Redmine: Completed: september 29th
Also, gosa will open up for non-developers. That means users can register at gosa. They will not receive push access to any of the repositories. But they will get access to reviewboard and redmine.
Opening for non-developers: Completed: september 9th
September 22nd
From this moment on users registered at gosa can request push-access to git and svn. They can do this by a special form. After approval from a supporter, they will be moved to the developers group and immediately get push access to both git and svn.
Completed: September 9th
September 29th
We will start approaching existing KDE projects on gitorious to move over. This period of a month will be used to move each and every project to our git repository. Projects of course have the right to stay on gitorious, but please note that at the end of the month the kde-developers groups will be deleted, meaning that you have to setup the access rights of gitorious differently to maintain access for all your developers.
git.kde.org open: september 29th
October 27th
The gitorious kde-developers group will be deleted. All projects that want to move, should have been moved to our git setup by now. All projects that did not move yet, are considered to want to stay on gitorious and don't want to be under the KDE umbrella any longer.
The git repository opens up for everyone willing to move to git. This will only apply to extragear and playground projects. We will *not* write any rules for the migration in any way, shape or form, but if you give us a .git file, we will be happy to create a project for you and import the code into the repository.
November 17th
After the initial flow of individual projects that have moved to git, we are open to assist in moving the KDE modules. How this part will happen is unknown and will probably not happen directly at this point in time.