[Kde-scm-interest] Moving kdebindings to git

[Eike Hein]

On 08/17/2010 07:36 AM, Andreas Pakulat wrote:
> On 16.08.10 18:04:55, Arno Rehn wrote:
>> Hi,
>>
>> currently kdebindings development (at least with regard to smoke, ruby, and 
>> csharp) is severly hampered by the fact that we're still using SVN - up to the 
>> point where people don't feel like committing their work because SVN is such a 
>> pain for them.
>> For that reason I'd like to ask if we can move the kdebindings module over to 
>> the kde git infrastructure earlier than the other modules. AFAIK amarok and 
>> konversation have already been moved there, so I guess it's already possible 
>> for the early adopter kind of people.
>>
>> I'm currently writing svn2git rules for kdebindings, so that part of the work 
>> is already being done.
>>
>> Would an earlier move be possible?
> 
> While causing some confusion, the kate team seems to sucessfully handle
> both svn and git. They're developing mainly in git now, but are porting
> all patches from git to svn and vice-versa. Of course you'd have to find
> one person who's able and willing to do this and understands enough of
> all the code to resolve conflicts.
> 
> And moving to git doesn't necessarily mean needing the KDE git
> infrastructure, there are other hosting solutions for opensource
> projects and as a git repo has the complete history its no big problem
> moving from one hosting to another...

For the record, I don't think KDE should offer its infra-
structure (Bugzilla, mailing lists, etc.) to projects that
are hosted outside the community. Currently the only way
for Git hosting is Gitorious.org + following the rules for
that[1], but once git.kde.org achieves general availabili-
ty, we're going to move KDE's projects from Gitorious.org
to git.kde.org and dissolve our presence on Gitorious.org.

Reasons for not allowing arbitrary hosting are preserving
KDE's commit-access-every-where culture and preventing frag-
mentation, having push logs for liability reasons, etc., and
the same reasons apply to not continueing our Gitorious.org
presence longer than necessary: Moving stuff to Gitorious.org
was only allowed under the assumption that KDE at large was
to follow in the first place, which we now know is not going
to happen, so git.kde.org is the only way to keep everything
together. Plus maintaining two places causes a sysadmin over-
head the sysadmin team is not willing to shoulder indefini-
tely.

For kdebindings this means you could either wait until git.k.o
becomes available to you, or do a temporary stint on Git-
orious.org and later move over to git.kde.org assuming the
release-team signs off on that.


1 =
http://techbase.kde.org/Development/Tutorials/Git/KdeOnGit#How_KDE_projects_on_Gitorious.org_are_set_up


> Andreas

-- 
Best regards,
Eike Hein