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

[Ian Monroe]

2009/7/3 Chani <chanika at gmail.com>:
>
>> 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?)

Basically this is the sort of thing I worry about when it comes to not
having root @ gitorious.org: not being able to tune push -f and branch
deletion rules, or whatever easily. We have to wait for Johan to
implement the features (and if he really does do the push -f stuff, he
is certainly fast though) or write some complicated web service to
react to triggers when it would've been straightforward if we just had
normal git access.

Note that the push -f and branch creation/deletion is tricky since (in
the latter case anyways) we will want to allow it in some
circumstances, but we don't want some n00b accidentally deleting
master branches. :)

Another issue is that I wonder if gitorious teams scale up to a
thousand members.

Anyways I overall think its a good idea. I'm just frustrated that we
had to push back deploying Gitorious.org for Amarok this last weekend
due to the push -f issue.

Ian