[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Concluding the Gitlab Discussion
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2019-03-23 20:15:31
Message-ID: CA+XidOFH2icndoTxO9232nHgo8U1qMia0iNppXpmOLZyLd35-Q () mail ! gmail ! com
[Download RAW message or body]

On Sun, Mar 24, 2019 at 8:46 AM Tomaz Canabrava <tcanabrava@kde.org> wrote:
>
> People, and the apps that are still in svn, like kmldonkey, will be migra=
ted too ?

Subversion will not be impacted in any form.
They'll remain outside of Gitlab.

Cheers,
Ben

>
> Em s=C3=A1b, 23 de mar de 2019 =C3=A0s 03:31, Ben Cooksley <bcooksley@kde=
.org> escreveu:
>>
>> On Tue, Mar 19, 2019 at 9:26 PM Ben Cooksley <bcooksley@kde.org> wrote:
>> >
>> > Hi all,
>> >
>> > Over the past few weeks we've had a discussion on whether we'd like to
>> > migrate from Phabricator to Gitlab, for handling both our code reviews
>> > as well as internal tasks (user facing bug reports are explicitly out
>> > of context at this time)
>> >
>> > Based on the comments the overall consensus seems to be at this stage
>> > to favour switching to Gitlab.
>> >
>> > This however is subject to a caveat around multiple task boards, which
>> > would be needed for larger projects to effectively coordinate amongst
>> > the various sub-projects.
>> >
>> > As part of the transition we will also arrange for the email interface
>> > to be enabled (for emailing in patches) and for the default for merges
>> > to be rebase when it's not a fast forward merge for all repositories.
>> >
>> > Does anyone have any final comments?
>> >
>> > In terms of the steps forward from here, Sysadmin will need a bit of
>> > time to prepare various parts of the infrastructure for the transition
>> > (such as the anongit network, which will need a full rebuild as part
>> > of switching).
>> >
>> > Once this is complete, we'll be in touch with more information on how
>> > the transition will take place.
>>
>> As it has now been a month since the initial thread was opened, and
>> with no final comments aside from Nate's over the past couple of days,
>> it seems that everyone is happy with the above as the community
>> consensus.
>>
>> We'll now proceed with preparing for a migration to Gitlab, subject to
>> the above caveat of getting multi-project boards (and with a request
>> to see if we can get merge request approvers sorted as well if
>> possible)
>>
>> >
>> > Thanks,
>> > Ben Cooksley
>> > KDE Sysadmin
>>
>> Regards,
>> Ben
[prev in list] [next in list] [prev in thread] [next in thread]