Using Gerrit for code review in KDE

[Aaron J. Seigo]

On Tuesday, September 9, 2014 18.32:41 Pier Luigi Fiorini wrote:
> 2014-09-09 17:39 GMT+02:00 Aaron J. Seigo <aseigo at kde.org>:
> > [1] even if I have my personal doubts w/regards to gerrit's
> > appropriateness
> > for KDE
> 
> Probably I'm too late for the party, but have you considered gitlab?

Yes; I helped trial it for the sys admin team along with the GCompris project. 
The user experience was really quite good, though the patch review was the 
weakest point though pretty much every issue I had with it was in their issue 
tracker with some being actively worked on.

The sysadmin team had some issues with the backend in terms of scaling to 
KDE's requirements.

I do agree that an all-in-one githubish experience is generally superior to a 
cobbled together geekyard; you have one tool to learn and use and developers 
are typically used to that workflow these days.

There are other options out there that provide that kind of user experience 
such as gogs.io and phabricator. I haven't used either, though, so can't speak 
to them ...

-- 
Aaron J. Seigo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20140909/52a99cd3/attachment.sig>