1790301 - New ICU4X license

Status: RESOLVED FIXED

(Core :: Internationalization, enhancement, P1)

Description

[Makoto Kato [:m_kato]]

ICU4X license is approved by bug 1715232, but current license is "Unicode-DFS-2016" by https://github.com/unicode-org/icu4x/pull/2303. So ./mach rust vendor will be failure when adding ICU4X modules.

Comment 1

[Makoto Kato [:m_kato]]

From ICU58, source code license is changed from ICU License to Unicode DFS 2016 according to https://unicode-org.github.io/icu/userguide/icu4c/faq.html#how-is-icu-licensed.

Unicode License is already in about:license (https://searchfox.org/mozilla-central/rev/9769b513e38ee4f5df9d5d1eff55ff7cdc8cbf81/toolkit/content/license.html#181)

Comment 2

[Makoto Kato [:m_kato]]

Hi, Mike.

We are considering to add ICU4X in Gecko. Although you approve old ICU4X license by bug 1715232, ICU4X license has been changed to Unicode-DFS-2016 that is same as ICU4C in intl/icu.

When adding ICU4X crate to Gecko, should we add the directory in https://searchfox.org/mozilla-central/rev/0948667bc62415d48abff27e1405fb4ab4d65d75/toolkit/content/license.html#5735-5738, then should we update vendor_rust.py to add a crate to RUNTIME_LICENSE_PACKAGE_WHITELIST? Or should we only add Unicode-DFS-2016 to RUNTIME_LICENSE_WHITELIST simply?

Comment 3

[Makoto Kato [:m_kato]]

Attachment: Bug 1790301 - Allow Unicode-DFS-2016 license to import ICU4X 1.0. r=mhoye

By bug 1715232, we added ICU4X license SHA256 hash to whitelist. But when
releasing ICU4X 1.0, license becomes Unicode-DFS-2016 like ICU4C. So I would
like to allow this license to import ICU4X 1.0.

Also, due to dependencies, some crates still use old ICU4X license. Although it
will be fixed by 1.1 release, we keep this hash.

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f82775fcc3f3
Allow Unicode-DFS-2016 license to import ICU4X 1.0. r=mhoye,glandium

Comment 5

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/f82775fcc3f3