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

List:       kde-community
Subject:    Re: github, phabricator: a new threadZ
From:       Eike Hein <hein () kde ! org>
Date:       2017-08-09 14:26:14
Message-ID: 4FD032E1-E3A5-4795-B049-D9B27C379FCD () kde ! org
[Download RAW message or body]

On August 9, 2017 9:10:15 PM GMT+09:00, Jos van den Oever <jos@vandenoever.info> wrote:
>Op woensdag 9 augustus 2017 13:50:46 CEST schreef Harald Sitter:
>> On Wed, Aug 9, 2017 at 1:39 PM, Boudewijn Rempt <boud@valdyas.org>
>wrote:
>> > On Wed, 9 Aug 2017, Riccardo Iaconelli wrote:
>> >> This is a new thread entirely, but incidentally also something we
>> >> should also think about. Why many KDE developers choose github
>instead
>> >> of scratch KDE repositories to start new software, where it could
>> >> happily be hosted within KDE infrastructure?
>> > 
>> > Our infra doesn't offer scratch repos anymore, does it?
>> 
>> It does, they were slated for removal with the transition to phab,
>> since that hasn't happend yet though I assume scratch repos are still
>> a thing. Albeit, a thing that is meant to be removed with (currently)
>> no replacement planned which is why for example I do not create any
>> new ones and instead use github. Although TBH the UX of creating a
>> scratch has also left me wanting as it entails me googling how to
>> setup a scratch every single time.
>
>Scatch repos are awesome! No need to open a browser, just push to a
>url. I was 
>very happy when I discovered KDE infra had such a lovely feature.
>
>Cheers,
>Jos

Yeah, I use them all the time, too.

Cheers,
Eike
-- 
Plasma, apps developer
KDE e.V. vice president, treasurer
Seoul, South Korea
[prev in list] [next in list] [prev in thread] [next in thread]