MPL License - Exhibit B

[giovannicintolo]

Product

axe-core

Question

Dear axe team,

I am working on an open-source project distributed under the GPL v3 with a linking exception. While reviewing libraries for inclusion, we noticed that your library, axe, is licensed under the MPL 2.0, but it includes Exhibit B ("Incompatible With Secondary Licenses").

This addition creates an issue for using axe in our project because it prevents the relicensing of your code under the GPL. Our project also integrates other GPL v3 libraries, and the presence of Exhibit B makes it impossible to include axe, even with the linking exception in place.

We would like to ask whether the inclusion of Exhibit B was an intentional decision or if it might have been added unintentionally or without fully considering its implications. Allowing axe to be used in GPL projects would greatly benefit the open-source community and could increase the adoption of your library.

Thank you.

[WilcoFiers]

@giovannicintolo can you provide more details about what you are hoping to do with axe-core, and why axe would need to be relicensed for that?

[dylanb]

We only want one license for all copies and derivatives of axe-core. Nobody is allowed to re-license axe-core or a derivative under any terms except the ones in our license. This is intentional.