Splitting Craft, move the recipes to GitHub

[Ben Cooksley]

On Thu, Aug 24, 2017 at 2:45 AM, Hannah von Reth <vonreth at kde.org> wrote:
> Is there any chance for bidirectional mirroring, so that KDE projects
> could easily apply
> pull request of non KDE members?
> The KDE bot reply to pull request is more than discouraging.

In theory one can still take pull requests from Github, as long as
they're pushed first to git.kde.org.
Our systems will then mirror it to Github automatically.

A full bi-directional mirror setup could potentially run into race
conditions if both change at the same time.

>From my understanding of how Github's systems work, they'll
automatically close pull requests as merged when they see the commits
appear in the actual repository, so this should work fine once the
auto-reply bot is switched off.

Cheers,
Ben

>
>
> On 23/08/2017 16:24, Sebastian Kügler wrote:
>> On woensdag 23 augustus 2017 15:38:38 CEST Luigi Toscano wrote:
>>> On Wednesday, 23 August 2017 15:33:09 CEST Hannah von Reth wrote:
>>>> We have been thinking about splitting the Craft recipes into a separate
>>>> repository for some time now.
>>>> To have a Craft core and the recipes separated would enable us to
>>>> provide more stable user experience. It would allow us to use the latest
>>>> recipes with the stable core.
>>>>
>>>> At the same time Craft tries to get rid of the image as the KDE Windows
>>>> build tool.
>>>>
>>>> Craft offers recipes for many libraries and non KDE applications.
>>>> Additionally Craft offers support for Mac, Linux and FreeBSD.
>>>>
>>>> In order to reach more people we intend to move the recipes to GitHub to
>>>> enable non KDE contributors to add their recipes.
>>>> Craft would continue to be a KDE Project on the KDE infrastructure, only
>>>> the recipes would move.
>>> Does it mean that people who want to contribute to recipes for applications
>>> developed by KDE should go to github?
>>>
>>> This is more or less the same as saying "so to get rid the image of kdelibs,
>>> let's put Frameworks on github only".
>>>
>>> I'm a bit sad.
>> I agree, these things should really be on KDE infrastructure. I won't repeat
>> the long discussion we had about github for KDE or not, but most of the
>> arguments also apply here. I think this case is really stretching where what
>> we want to achieve with KDE's manifesto, and as a community. Moreover, it
>> seems counter-productive to have code and recipes split on two services.
>>
>> Could you not merge these things from github somehow, so that we can keep the
>> canonical copy on KDE's git, or perhaps also pull recipes from github, *in
>> addition to* KDE's git?
>
>