<rbrunner7> For better visibility, I repost what tevador posted on IRC while Matrix was down: tevador/polyseed #24

<rbrunner7> I am not well versed with such licensing stuff. Does that make our case easier? I guess yes from first positive reactions to this (also only on IRC)

Apache 2.0 is permissive and allows shipping in closed source including modifications, though as usual it has attribution clause (license/notice info)

<jpk68:matrix.org> IIUC, adopting an Apache 2.0 dependency would mean that release binaries are legally a "combined/derivative work"

<jpk68:matrix.org> So we would still have to distribute binaries with Apache license info

They already have a LICENSE file as distributed which contains 3 different copyright entries. BSD-3-CLAUSE, MIT, and "Parts of the project are originally copyright (c) 2012-2013 The Cryptonote developers" (no standard license claimed)

As a nit while the project repo has a LICENSE file with copyright updated to 2024, the LICENSE file which ships still uses 2022 as copyright year.

from checking the recent monero-gui v0.18.5.2

<rbrunner7> So we add an Appache 2.0 license text to those files, update the years of course, and then we are probably good to go regarding Polyseed after that PR 24 is merged?

<jpk68:matrix.org> No, for the source code, we're fine just having tevador's Apache copyright comments in the vendored/submodule'd source files.

<jpk68:matrix.org> The potential issue is for release binaries, where we would have to distribute Apache license text as well, with the binaries

<jpk68:matrix.org> Sorry, maybe you were referring to that?

<rbrunner7> Yes, I am talking about that, the release binaries. Where we already pack a license file into ZIP files, and the GUI installer also copies one, if I remember correctly

<rbrunner7> That sounds splendid

<tobtoht> With the relicensing to Apache 2.0 there is no conflict with (my interpretation of) the CoC now.

<tobtoht> As previously discussed, we should expose copyright notices and license info in the wallet api for downstream consumers, but this isn't a requirement for the polyseed PR since we don't do this for any third-party library currently.

<jpk68:matrix.org> I am fine with this as well

<rbrunner7> My sincere thanks and respect to tevador for doing this Polyseed relicensing.