Phabricator: All repositories registered - upcoming workflow changes

[Ben Cooksley]

On Thu, Feb 2, 2017 at 7:01 AM, Milian Wolff <mail at milianw.de> wrote:
> Hey Ben

Hi Milian,

>
> forwarding this mail from Francis, as his points resonate deeply with me

He resent it to all lists, i'll be responding to it shortly.

>
> I'm all for killing phabricator, but only in the sense of pushing it into a
> read-only mode. Please lets not lose the valuable information stored there!

Killing Phabricator?

Cheers,
Ben

>
> ----------  Forwarded Message  ----------
>
> Subject: Re: Phabricator: All repositories registered - upcoming workflow
> changes
> Date: Wednesday, February 1, 2017, 11:26:54 AM CET
> From: Francis Herne <mail at flherne.uk>
> To: kdevelop-devel at kde.org
>
> Hi,
>
> First off, there's a lot of postponed, or at least possibly-useful,
> work on ReviewBoard which would be lost. Some of this is from newish
> contributors who might be discouraged - e.g. the author of
> https://git.reviewboard.kde.org/r/129589/ mentioned on IRC the other
> day that he's hoping to complete it at some point.
>
> For already-committed work:
>
> Even if the mail-archiving infrastructure was in a useful state, this
> would be inconvenient - there are more than a *thousand* REVIEW: tags in
> kdev* project commits, plus several comments with "see <review url>".
>
> Many mailing lists aren't logged at all, there's no internal
> search with only patchy Google indexing, and 'browsing' the archive
> means clicking through arbitrarily-grouped mails by date with minimal
> threading. That's not merely inconvenient, it's going to cause a
> catastrophic loss of information.
>
> Please reconsider.
>
> -Francis
>
> On Wed, 1 Feb 2017 07:56:52 +1300
> Ben Cooksley <bcooksley at kde.org> wrote:
>
>> On Tue, Jan 31, 2017 at 11:36 PM, René J.V. Bertin
>> <rjvbertin at gmail.com> wrote:
>> > On Sunday January 29 2017 08:32:21 Ben Cooksley wrote:
>> >
>> > Hi,
>>
>> Hi Rene,
>>
>> >
>> > >From this point forward, communities should be moving away from
>> >>Reviewboard to Phabricator for conducting code review. Sysadmin will
>> >>be announcing a timeline for the shutdown of Reviewboard in the near
>> >>future.
>> >
>> > I hope that shutdown doesn't mean complete disconnect; it would
>> > probably be a loss of as-yet unknown importance if all code reviews
>> > become unavailable.
>> >
>> > I'll miss ReviewBoard. Phabrithingy may be more powerful and
>> > versatile, but RB had its advantages too which could be why it's
>> > still being used (quite a lot, as far as I can see) and hasn't been
>> > integrated with KDE's own IDE yet.
>>
>> It will be a complete shutdown of Reviewboard - we'll be archiving it
>> in the event for some reason it becomes necessary to access the data
>> it stores.
>>
>> In most cases mailing lists should have the history of reviews in
>> their archives, so those will continue to be accessible through list
>> archives in the long run.
>>
>>
>> >
>> > R.
>>
>> Cheers,
>> Ben
> -----------------------------------------
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de