Can you relicense it to permissive, for potential interested contributors?

[kevincrans]

Having created an alternative implementation of Metal is marvelous!
From every-day tasks to gaming, it's a leap in open-source software.

Could you consider relicensing this to MIT/BSD-2(/Apache), so one of the RavynOS developers, the now Darwin-based OS that tends to be an open-source macOS alternative that sticks to permissive licenses like Zoe, could perhaps help develop it further and implement a build in their own OS that lacks this capability?

Thank you very much if you read this, and even more if you approve!

[CuriousTommy]

@bugaevc & @LubosD, what are your thoughts on this?

I think there is a real-world benefit to having us share some of our code with the RavynOS developers (and vise-versa).

Could you consider relicensing this to MIT/BSD-2(/Apache)

If we did go down this route, I would personally prefer the code to be licensed under MPL2 (as a middle ground between GPL and MIT).

[bugaevc]

If this was about Darling as a whole, my thoughts would be "absolutely not"; for darling-metal however I could see the appeal. You'd want to ask @facekapow anyway, not me.

Could you consider relicensing this to MIT/BSD-2(/Apache), so one of the RavynOS developers [...] like Zoe, could perhaps help develop it further

Is there a real intention of Zoe to actively contribute if we were to relicense, or is it a hypothetical that perhaps RavynOS folks could be interested?

It's also worth noting that https://github.com/darlinghq/indium/ (and the upstream repo) is under a BSD license. Are RavynOS developers looking to contribute to indium or darling-metal specifically?

[CuriousTommy]

If this was about Darling as a whole, my thoughts would be "absolutely not"; for darling-metal however I could see the appeal.

Just darling-metal.

Is there a real intention of Zoe to actively contribute if we were to relicense, or is it a hypothetical that perhaps RavynOS folks could be interested?

It's also worth noting that https://github.com/darlinghq/indium/ (and the upstream repo) is under a BSD license. Are RavynOS developers looking to contribute to indium or darling-metal specifically?

@mszoek

[mszoek]

Hi! 👋🏼

I'm specifically interested in darling-metal (and I guess indium if that's a dependency) since we also need to write such a thing and it would be great to join forces on it. I just can't put GPL code into our frameworks (or most other areas). I am good with MPL!

I can't guarantee when I'll get to this... we recently decided to flip from FreeBSD to Darwin as a base so I'm busily hacking kernel and bootloader stuff at the moment, then there's lots of other desktop implementation stuff before we get to Metal. But I'm definitely interested in contributing to it and using it here at some point.

Honestly y'all are doing great stuff and I'd love to be able to use more of it and contribute back.

[facekapow]

Hey everyone!

If this was about Darling as a whole, my thoughts would be "absolutely not"; for darling-metal however I could see the appeal. You'd want to ask @facekapow anyway, not me.

Personally, I'd be fine with re-licensing this specific component. I would also be against re-licensing Darling as a whole, but I think darling-metal makes sense.

If we did go down this route, I would personally prefer the code to be licensed under MPL2 (as a middle ground between GPL and MIT).

I agree that I like this as a nice middle ground; it should be compatible with a BSD-licensed project using it while still providing some copyleft protection against companies using it without disclosing the source.

I'm specifically interested in darling-metal (and I guess indium if that's a dependency) since we also need to write such a thing and it would be great to join forces on it.

That sounds great! Yes, Indium is actually the primary part of this component. This repository essentially implements a thin Objective-C ABI-compatible layer on top of Indium; all of the actual Metal-to-Vulkan translation is implemented there, including shader translation. This should probably be in a README for this repo 😄.

[CuriousTommy]

The only other contributor is @jlucfarias, but I don't believe it's necessary to get his permission since his code contribution so far are just stubs and basic variables.

[jlucfarias]

Well, if it will be useful for the continue and improvement of the project, I'm not against that and for now, as @CuriousTommy said, my only contributions are only stubs so I don't think I have something to be against (or not) of this.