Akonadi, Attica and Soprano moved to git.kde.org

Alexander Neundorf neundorf at kde.org
Wed Oct 27 20:23:29 BST 2010

On Tuesday 26 October 2010, Andreas Pakulat wrote:
> On 26.10.10 21:26:24, Alexander Neundorf wrote:
> > On Tuesday 26 October 2010, Andreas Pakulat wrote:
> > > On 26.10.10 20:55:51, Alexander Neundorf wrote:
> >
> > ...
> >
> > > > There's probably also somewhere a HOWTO hot to get the stuff from
> > > > there, how to commit, push, etc ?
> > > > Can you please post the link ?
> > >
> > > This has been explained quite a bit on planetkde by the sysadmins,
> >
> > were these blogs the official announcement ?
> They were official in terms of where the setup process for the new
> infrastructure stands.
> > I haven't seen any on k-c-d, maybe I missed it.
> Well, the kde core modules are not moving yet, so why would anything be
> announced here at this point?
> > What a search on techbase brings as first results doesn't look too
> > useful: http://techbase.kde.org/Special:Search?search=git&fulltext=Search
> The first 3 results are useful, additionally the amarok-related and the
> kdeongit page.

No, they are not.
First hit (Development/Tutorials/Git):
"Although KDE is currently using SVN, we're working on moving to git."
Doesn't sound like something up-to-date I feel like relying on.
The "Getting started" section lists more links to other articles.

Second hit (Development/Tutorials/Git/BestPractices):
Well, it's basically empty.

Third hit (Development/Tutorials/Git/Intermediate):
Hmm, basically empty too.

4th hit (Getting_Started/Sources/Amarok_Git_Tutorial):
Talks about amarok. I'm currently not interested in amarok in this regard.
Does this apply to the rest of KDE or kdesupport ?

> > We have hundreds of developers, IMO we need a simple step-by-step howto.
> But most of those don't build kdesupport stuff themselves (or even
> kdelibs). Also this is not really of concern to kde-core-devel, those
> projects in kdesupport don't belong to kde's core by definition. They're
> merely close dependencies.

Ok, as long as there is no howto count me out of caring about keeping 
kdesupport building.

This is what Brad from Kitware has written when they migrated cmake and their 
other projects from cvs or svn to git:

If I need to check something for how to deal with git for cmake, I can go 
there and look.
Still there were quite a few questions on the cmake-devel list (not only, but 
also from me) how to do something with git and how to handle issues which 
arise. And this with much less developers than KDE has and apparently much 
better documentation than we have.

I'm afraid we need similar or several of our developers will have problems.


More information about the kde-core-devel mailing list