Differences in licensing Android and iOS SDKs

[wzieba]

hi there 👋 I've noticed that Android SDK is released under Apache 2.0 (link) but iOS SDK under MIT (link).

We're considering using Unleash in our projects, but Apache 2.0 license is a blocker for us, as it's not compatible with GPL-2.0.

I have 2 question:

• what's the reason to use Apache 2.0 for Android SDK?
• if there are no blockers, would you consider updating Android SDK's license to MIT, the same like iOS?

[chriswk]

Hi.

1. The main reason was that our main repo unleash/unleash is also Apache 2.0, so was assumed by our developers to be our default license.
2. We'll double check the licenses of our dependencies and if no blockers can be found, we're happy to relicense it as MIT.

[chriswk]

I made Unleash/unleash-android#95 to make sure we follow up

[gastonfournier]

Hi @wzieba we don't have anything licensed under MIT. The swift repository you linked is from a different company.

Why is it a requirement for you to be GPL-2.0 compliant? It's the first time in 10 years we get a request like this, so we'd like to understand why this change is needed for you.

[wzieba]

The swift repository you linked is from a different company.

Sorry! I was researching different solutions and confused links.

Why is it a requirement for you to be GPL-2.0 compliant?

Several of our projects at Automattic, including the WordPress and WooCommerce mobile apps for both Android and iOS, are released under the GPL-2.0 license. Consequently, the licenses of our dependencies must also be compatible with GPL-2.0 requirements.

[gastonfournier]

Thanks @wzieba we're going to look into this and make sure we can make this change safely. Thanks for the feedback!