[Kde-scm-interest] Proposal: Migrating KDE to Git...orious.org

[Chani]

> S1) Commitfilter
>
> Although running arbitrary shellscripts on Gitorious.org as git hooks is
> not allowed for security reasons, Johan is planning to add support to
> POST the data of commits to URLs (it's in a branch that will be
> integrated soon). This will allow you to supply one or more callback
> URLs for a repository, so whenever someone pushes the details of the
> commit are POSTed via HTTP to the callback URL(s) as JSON. It includes
> items like the actual commit, who pushed it, and the before/after SHAs.
>
> This could be used (with IP-based access control for security) to still
> be able to provide commitfilter-like functionality (although
> commitfilter as it exists would likely need to be updated as a result of
> the SCM difference in the first place).

what about BUG:, CCMAIL:, etc?could it provide hooks for that too?
I guess whatever server the callback goes to could do anything with the data, 
right? but someone would have to set up such a server and (re)write all the 
scripts...

so... do we have someone willing and able to do that? I don't know a thing 
about this web stuff.

is there any chance gitorious would be willing to make an exception to this 
no-scripts rule for KDE? if so, how much work would it be to write *those* 
scripts? (ie, would it be less work than doing this http hook thing?)

>
> S2) Capacity
>
> Capacity is a concern, as KDE would become the largest project both in
> terms of source code and activity. When these issues was posed to Johan,
> here was his answer:
>
> 'We should look into some kind of general mirroring facility in the long
> run (not really because of bandwidth used, but also more to speed up
> transfers on other continents). We do pay for SAN storage and bandwidth,
> but there's "plenty available" as long as we pay for it.'

so... who's going to pay for it in the end? do we need to rely on nokia for 
this? if not, would the amount be small enough for the e.V to easily pay it? 
I've no idea how much bandwidth we eat with svn. 
if something goes wrong and somehow we don't have the money for it any more 
(quite unlikely I hope) I guess it's just a matter of putting a copy of the 
repo back on one of our own servers?

one more question: is this worth the money when we can do it ourselves for 
free? it does sound like we get a lot for that money (including dirk not 
having to do as much work).

>
> * The servers currently used by KDE for distributing code via Subversion
> could become a part of a wider Gitorious.org infrastructure, acting as
> local mirrors and distribution centers for the subset of KDE
> repositories and clones. This benefits both KDE and Gitorious.org by
> speeding up transfers to various parts of the world, increasing
> redundancy, and easing the burden on the main site. For instance, KDE
> could handle reads on the various KDE repository and clones, while
> pushes still go to the main server. This would significantly cut down on
> bandwidth at the main Gitorious.org site.

mirrors++

>
> Johan is working on getting an estimate for the cost of a SLA for KDE.

SLA = ...server license agreement? :)
estimates are good.

>
> C2) What happens if Gitorious.org goes down, how long would it take to
> get it up and running again?
>
> Johan's answer:
>
> '"if there's a bug, how long does it take to fix?" :)
>
> In the case of hardware failures, we do have redundant hardware. We
> currently run Gitorious.org on two sun x4150's with 32GB of ram,
> connected to a SAN (over FiberChannel) where the actual Xen images and
> repository data etc is stored. The machines only utilitize 50% of the
> resources that can't be grown or shrunk, so we can move the images
> between them in case of hardware failure.'

gitorious.org was down inconveniently when scripty was updating last week. 
this won't matter so much after I make scripty's git stuff a bit more robust, 
but... how often does gitorious go down for upgrades or whatever it was?

> easily. Johan has indicated that he would be willing to help us migrate
> and be willing to prioritize adding features or fixing bugs that we
> would discover or need short-term as we migrate;

that's a big plus. :)

> in addition, he is also
> happy to discuss having our help and input with system administration
> should we want it, which helps ensure that we have both a stake in the
> project and an exit plan should an unfortunate situation arise.

yay :)

>
> Gitorious.org is the logical choice for hosting our Git repositories
> compared to hosting it ourselves, and should be given serious
> consideration.

sounds pretty good to me... someone offering to do a bunch of work for us and 
fix bugs that we need fixed and so on... :) the only thing that concerns me is 
the money part, but if nokia's willing to pay for it then that should be fine 
:)

-- 
This message brought to you by eevil bananas and the number 3.
www.chani3.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20090703/200012f3/attachment.sig