Seems to me y'all aren't appreciating that I am telling you my point
of view. I have created some 20 repos on github last year and 0
scratch repos on our infrastructure. I thought you might want to know
why. Feel free to find my reasons silly, that doesn't change them
though.

I am did not mean to argue any side.

On Thu, Aug 10, 2017 at 9:02 AM, Harald Sitter <sit...@kde.org> wrote:
> I for one would pick the alternative which is not using our
> infrastructure and instead click two buttons so I don't have to file
> paperwork manually nor have to wait for said paperwork to get faxed to
> HQ for approval. i.e. not waiting trumps waiting in my world.
>
> On Wed, Aug 9, 2017 at 8:05 PM, Albert Astals Cid <aa...@kde.org> wrote:
>> El dimecres, 9 d’agost de 2017, a les 13:50:46 CEST, Harald Sitter va
>> escriure:
>>> On Wed, Aug 9, 2017 at 1:39 PM, Boudewijn Rempt <b...@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
>>
>> That was not the plan, the plan (unless it has changed since last time i
>> asked) is to have a team of "trusted people" that can create repos on
>> phabricator, so basically you'd open a ticket and you'd get a repo created in
>> a matter of minutes, not automagic, but surely you can continue coding for 15
>> minutes while you wait for your repository to be created.
>>
>> Cheers,
>>   Albert
>>
>>> 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.
>>>
>>> HS
>>
>>

Reply via email to