Hello libultrahdr team!
I am a WordPress core committer, currently working on a project to bring modern image processing to WordPress via client side media processing and would love to add support for UltraHDR images to the ~35+% of the web using WordPress. However the current Apache2.0 license is not compatible with the WordPress GPLv2 license (I am not a lawyer, but have confirmed this with one). Would you consider dual licensing under the Apache License 2.0 and BSD 3-Clause?
A maintainer of the libvips library suggested this in a comment, mentioning that Highway took a similar approach to ensure compatibility with NumPy's BSD-3 license (see e.g. the removed licensing paragraph in commit numpy/numpy@f09ab71).
If this is not feasible we will not be able bundle UltraHDR support directly with WordPress (forcing users to install a separate plugin to get support) which would be a huge loss for the web, one of the main potential beneficiaries of UltraHDR imagery.
cc: @gregbenz
Hello libultrahdr team!
I am a WordPress core committer, currently working on a project to bring modern image processing to WordPress via client side media processing and would love to add support for UltraHDR images to the ~35+% of the web using WordPress. However the current Apache2.0 license is not compatible with the WordPress GPLv2 license (I am not a lawyer, but have confirmed this with one). Would you consider dual licensing under the Apache License 2.0 and BSD 3-Clause?
A maintainer of the libvips library suggested this in a comment, mentioning that Highway took a similar approach to ensure compatibility with NumPy's BSD-3 license (see e.g. the removed licensing paragraph in commit numpy/numpy@f09ab71).
If this is not feasible we will not be able bundle UltraHDR support directly with WordPress (forcing users to install a separate plugin to get support) which would be a huge loss for the web, one of the main potential beneficiaries of UltraHDR imagery.
cc: @gregbenz