License?
Is this supposed to be available under the same license as Vulkan Tools (Apache 2.0) or libstrangle (GPL 3.0)? Or something entirely different?
TBH, I'm not sure.
I don't want to restrict it in any way, so maybe I could pick an mit/zlib/wtfpl as license.
Also, I don't want to create any inconveniences for users of this piece of code.
But, it's not clear for me how Vulkan Tools layer factory projects should be licensed.
Since this repo don't contain any modified files from Vulkan Tools, I believe I'm not sticked to Apache 2.0 license. Still can't change LUNARG in the layer name w/o modification.
Also, it's a reinterpretation of libstrangle's code.
So probably I can't use anything other than GPL 3.0. I'll appreciate any help with this licensing issue.
The Apache license is basically the same spirit as MIT/zlib (but with some additional patent protection, which is probably reasonable for any Vulkan stuff), so it might make sense to aim for that. However, you are also right that if the libstrangle code base served was used as a basis for this, the virality of the GPL probably means that this has to be GPL as well.
I’d probably personally go for GPL for now and maybe reach out to libstrangle’s author and ask for permission to (re)license VkGHL under Apache 2.0. Even if it may not be 100% necessary, the granting of such a permission would ensure using that license is both legally and morally right. :)
Another option is to reimplement it as pure Vulkan layer and PR to libstrangle.
But I'm not sure if libstrangle’s author interested in such PR. Also I don't mind if someone else would do this, then I just mark this project as deprecated/superseded.
I actually came here because strangle wasn’t working for me. :) (I also didn’t manage to get VkGHL working yet, but that’s a topic for another issue, if anything…) Getting this in there would be very nice with regards to not fragmenting the "gaming toolbox" more than "necessary".
I also didn’t manage to get VkGHL working yet, but that’s a topic for another issue, if anything…
I updated README, hope this will help with your issue.