On Wed, Dec 17, 2014 at 10:23 AM, Jan Kundrát wrote:
> Hi Ben,
Hi Jan,
>
>> It isn't just
>> the tool itself which has to be maintained: we have commit hooks,
>> integration with other bits of infrastructure and so forth which also
>> needs to both be implemented and maintained.
>
>
> In case of
(Adding kde-core-devel as this is a global Gerrit thing.)
On Tuesday, 16 December 2014 23:01:44 CEST, Thomas Lübking wrote:
Would it be possible and make sense to have the build service
send mails only
a) on failure
We could do that, the options are at [1]. However, see below.
b) to the com
Don't want to weigh in on Gerrit as I don't know it well enough, but as
for Phabricator, Ben may have forgotten but we did evaluate it a while
back. It was neat but had a very serious problem: you needed an account
to even view anything (no public access), and once you got into it
everything wa
On 12 Dec 2014, at 17:25, Luca Beltrame wrote:
Albert Astals Cid wrote:
So what do you suggest, because we already tried gitlab and didn't
work,
is there any more github clones out there that may work for us? I
don't
There are at least a couple:
- Gitbucket (written in Scala, mimics the Gi
Hi Ben,
It isn't just
the tool itself which has to be maintained: we have commit hooks,
integration with other bits of infrastructure and so forth which also
needs to both be implemented and maintained.
In case of Gerrit, there is no need for custom hooks as they stay on
git.kde.org, and ther
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/121477/
---
(Updated Dec. 16, 2014, 12:12 p.m.)
Review request for KDE Software on Ma
On Monday, 15 December 2014 22:25:37 CEST, Kevin Kofler wrote:
That creates the situation that "we
either all switch and have uniformity or we don't and then we end up with
reviewborad+gerrit" (Albert Astals Cid), which to me sounds a lot like
blackmail (of course not by Albert, he's just the m
