Sysadmin report on the modernization of our infrastructure

[Helio Chissini de Castro]

Thanks Ben for the right proposal.

During the process when the original thread becomes a hell of bickering
people defending his point instead of a concise approach, i almost loose
the faith on results.

I personally tested several of the tools on the last job, where i managed
internally the buildsystem, so i vow for phabricator as a good decision.
I really don't like gerrit, and my experience with it sometimes remove me
from want to do things.

Phabricator is the obvious system to go. We trusted our sysadmins decisions
for years, would not be different now.

Helio



On Wed, Jan 21, 2015 at 9:07 AM, Martin Klapetek <martin.klapetek at gmail.com>
wrote:

> On Wed, Jan 21, 2015 at 5:12 AM, Ben Cooksley <bcooksley at kde.org> wrote:
>
>> Hi all,
>>
>> As promised in the earlier thread, i'd like to present the sysadmin
>> report on the state of the infrastructure surrounding our code.
>>
>> It contains a detailed summary of what is broken with our existing
>> systems, why change is necessary and an evaluation of the options we
>> considered. We have also made a proposal based on our evaluations and
>> the wishlist of functionality drawn up the community.
>>
>> Please find it attached - and let us know what you think. Feedback is
>> welcome.
>>
>
> Thanks a lot Ben for this, very comprehensive document.
>
> One question about Phabricator - in the discussions before the RB web UI
> and uploading patches via web was mentioned a lot, will uploading diff
> through
> web interface still be possible via Phabricator or is the Arcanist thing a
> must?
> This isn't clear from the report.
>
> Cheers
> --
> Martin Klapetek | KDE Developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20150121/f4800bad/attachment.htm>