Splitting Craft, move the recipes to GitHub

[Hannah von Reth]

Thanks for all input.

We will split the recipes from the Core to a new KDE repository.
When multiple repositories and cross repository dependencies are properly
implemented in Craft, the recipes will be split again.

One repository containing non KDE recipes,
this repository will be located on GitHub.

A second repository will be located on the KDE infrastructure,
containing KDE recipes.

On the user side nothing should change.

Cheers,

Hannah

On 23/08/2017 17:42, Christian Mollekopf wrote:
> On Wed, Aug 23, 2017, at 03:33 PM, Hannah von Reth wrote:
>> Hi everyone,
>>
> Hey,
>  
>> 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.
>>
> I think that is an excellent idea =) It would allow people like me to
> maintain a stable
> set of buildscripts while being able to use the latest of the buildtool
> itself.
>
>> 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.
> Neat!
>
>> 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.
> Enough has probably been said about that.
> Maintaining the KDE buildscript on KDE infrastructure makes a ton of
> sense to me. Having a separate repository on github for more github
> focused projects also makes a lot of sense to me (the alternative being
> to have a read/write mirror).
>
> I think having to deal with multiple repositories will introduce some
> additional complexity as you might need to allow dependencies between
> them, but I also think it would be a very valuable feature.
>
> Anyways, I'd just put the KDE buildscripts on the KDE infra, create a
> github mirror for now, and then in the long run work on repository
> dependencies so it's not necessary to duplicate buildscripts in all
> repositories.
>
> Cheers,
> Christian


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20170824/c6b8215e/attachment.sig>