[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] KDE Git hosting status update
From:       Jeff Mitchell <mitchell () kde ! org>
Date:       2010-06-10 18:22:30
Message-ID: 4C112D66.2010200 () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On 6/10/2010 12:07 PM, Eike Hein wrote:
> What we're not going to do, at least initially, is to allow
> outside people to make an account with us and create perso-
> nal clones of KDE repositories on our infrastructure. But
> that is not a software question; it would have been the same
> had we chosen to install Gitorious.
>=20
> Note however that KDE developers are going to be able to
> create personal clones.

Right. So as far as patches from random users, we end up in the same
boat regardless of Gitorious vs. something else, because we're not
prepared to open up a local Gitorious instance to the wide world.

As a result, it actually made the comparison a bit easier  :-)

That said, the workflow of Gitorious -- before they added the feature to
pull the refs into the originating repo (which as Eike explained could
actually be a *bad* thing) -- was to give you a set of instructions on
adding the other repo as a remote, checking out the feature branch, and
doing the merge. This could still occur -- it'd be nice if we find a way
to have that workflow automatically generated, but certainly users could
clone a repo, push up to Gitorious, GitHub, or their other preferred Git
hosting solution, and then send us information as to the location,
branch, and range of commits.

--Jeff


["signature.asc" (application/pgp-signature)]

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest


[prev in list] [next in list] [prev in thread] [next in thread]