[Kde-scm-interest] KDE Git hosting status update

[Eike Hein]

On 06/11/2010 09:42 AM, Andreas Pakulat wrote:
> On 11.06.10 09:00:27, Eike Hein wrote:
>> On 06/11/2010 08:44 AM, Oswald Buddenhagen wrote:
>>> does reviewboard support reviewing entire branches like gitorious does?
>>
>> I *think* post-review by now has some level of support for posting
>> a series / selection of git commits as a patch series to ReviewBoard,
>> so that you can put up the extra commits in a branch, but I'm not
>> sure.
>>
>>
>> A few more general comments wrt/ "off-repo" feature branches:
>>
>> One thing to keep in mind is that even if we had decided to install
>> the Gitorious software, we would not have allowed free-for-all sign
>> up (administrative overhead, capacity, liability, etc.), so the merge
>> request facility would not be available to external contributors.
> 
> I think this will really be the big factor in our git-setup.

Sure -- I mean it's not like we didn't have reasons to pursue
Gitorious.org (i.e. the site run by Shortcut) originally, but
it didn't work out, so now we have to move on. And in looking
at our options for self-hosting, weighing the pros and cons
and what we can provide, what's in the report is what we arri-
ved at.

And let's keep in mind that while a bunch of us have been using
Gitorious, the majority of KDE is still stuck in SVN, due in
large part because we were blocked on the hosting decision -
now we can get the ball rolling again, and there are definitely
other benefits going Git delivers to those currently stuck with
SVN than just Gitorious' merge request feature.

Who knows, maybe in the future we will figure out a way to
provide repo hosting to outsiders.

Or, and this strikes me as a much more interesting/likely one,
ReviewBoard could evolve the ability to stuff the content of
review requests as refs into the target repositories (it does
already interact with the repositories, so this is not entirely
far-fetched) so that you can fetch and merge them exactly the
same way you currently do on Gitorious (remember: the content
of a merge request is not stored in the requestee's personal
clone repo, but as refs in the repo the request is for).

Since we are coders, we could even look into working on that
ourselves.


> Andreas

-- 
Best regards,
Eike Hein